Method and apparatus for interworking between electronic devices

ABSTRACT

An electronic device comprising: a memory; a communication unit for exchanging communications with a wearable device and an external device; and at least one processor that is operatively coupled to the memory, configured to: detect an event that is associated with a connection with the external device; identify a function that is associated with the external device in response to the event; and transmit to the wearable device an instruction for executing the function, wherein the instruction is transmitted via the communications unit.

CLAIM OF PRIORITY

This application claims the priority under 35 U.S.C. §119(a) to KoreanApplication Serial No. 10-2015-0049767, which was filed in the KoreanIntellectual Attribute Office on Apr. 8, 2015, the entire content ofwhich is hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates to electronic devices, in general, andmore particularly to a method and apparatus for interworking betweenelectronic devices.

BACKGROUND

With the development of electronic device technology, a wide range ofservices, which are provided to the user, have rapidly increased. Forexample, the electronic devices provide a variety of functions, such asweb page-browsing, reproducing content, SNS (Social Networking Service)activities, photographing images, or recording videos, which may beperformed by the user by using the electronic devices, as well as aphone call function.

In addition, thanks to the development of information and communicationtechnology, general things as well as PCs (personal computer) or smartphones have been used as information communication terminals. Inparticular, the wearable devices that are information terminals, whichare put, or worn, on a user's body, have recently attracted wideattention. Initially, the wearable devices have been developed for aspecial purpose and have been targeted to a limited market, but now thewearable devices are developed and used in a form that normal consumersuse for usual purposes. The wearable device may represent an electronicdevice that may be put on a user's body. The wearable device does notrefer to a mere electronic device that may be put on the user's body,but it may refer to an electronic device that may communicate with theuser at the closest position to the user's body. The wearable devices donot need to be held or carried by a hand unlike the current electronicdevices (e.g., smart phones, tablet PCs, or the like), and the wearabledevices have an improved portability in order to thereby be worn on theuser's body or clothing in order to be used.

The wearable device may continue to collect detailed information of thesurroundings or a physical change of the user in real time. The wearabledevice may perform a function of acquiring, storing, and displayinginformation on its own, such as a clock, an alarm, or recording exerciseinformation. In addition, these days, the wearable device can perform afunction by interworking with the electronic device that the same userhas rather than a sole function of the wearable device. For example, newuser experiences, such as a voice recognition function, a gesturefunction, or a healthcare function, by making the electronic device andthe wearable device interwork with each other.

According to an embodiment, when a phone call function is executed inthe electronic device, the wearable device may perform a communicationfunction, such as a sound exchange with the electronic device.Accordingly, the user may make a call through a microphone (MIC) and aspeaker (SPK) of the wearable device as if he/she did in the electronicdevice. Alternatively, the wearable device may: display a numerickeypad; receive a user input, such as a user's touch; and instruct theelectronic device to perform the phone call function in response to theuser input. Alternatively, when a photographing function is executed inthe wearable device through a camera, the wearable device may transmitphotographed images to the electronic device in order to thereby enablemore convenient shooting compared to the electronic device and in orderto thereby compensate for disadvantages that occur due to theminiaturization and the small storage capacity of the wearable device.As described above, the wearable device may provide more extensive userexperiences by connecting to, and interworking with, the electronicdevice compared to the wearable device that is solely used.

SUMMARY

Aspects of the present disclosure are to address at least theabove-mentioned problems and/or disadvantages and to provide at leastthe advantages described below.

Accordingly, an aspect of the present disclosure is to provide a methodand an apparatus for making an electronic device, a device, and awearable device interwork with each other

Another aspect of the present disclosure is to provide a method and anapparatus, which may include an electronic device, a device, and awearable device, and may process an event related to the device byinterworking with the wearable device in response to the event due tothe device while the electronic device is connected with the wearabledevice.

Another aspect of the present disclosure is to provide a method and anapparatus in which an electronic device provides a wearable device withan event according to the connection or disconnection of another deviceother than the wearable device that interworks with the electronicdevice in order to thereby provide more convenient and wider userexperiences to the user.

Another aspect of the present disclosure is to provide a method and anapparatus, which may allow the electronic devices to interwork with eachother and may implement an optimal environment for performing theinterworking function corresponding thereto in order to thereby improvethe user's convenience and the usability of the electronic device.

According to aspects of the disclosure, an electronic device is providedcomprising: a memory; a communication unit for exchanging communicationswith a wearable device and an external device; and at least oneprocessor that is operatively coupled to the memory, configured to:detect an event that is associated with a connection with the externaldevice; identify a function that is associated with the external devicein response to the event; and transmit to the wearable device aninstruction for executing the function, wherein the instruction istransmitted via the communications unit.

According to aspects of the disclosure, a method is provided for use inan electronic device, comprising: establishing a connection with anexternal device; detecting an event that is associated with theconnection with the external device; identifying a function that isassociated with the external device in response to the event; andtransmitting to a wearable device an instruction for executing thefunction.

According to aspects of the disclosure, a method is provided for use ina wearable device, comprising: receiving an instruction from anelectronic device; executing a function corresponding to the instructionand displaying a user interface associated with the function; receivinga first input via the user interface; and transmitting a control signalto the electronic device in response to the first input.

According to aspects of the disclosure, a method is provided comprising:establishing a connection between an electronic device and a wearabledevice; detecting an event associated with the connection; displaying,by the electronic device, a first user interface that is related to afunction that matches an external device, and transmitting to thewearable device an instruction for executing the function; displaying,by the wearable device, a second user interface that is related to thefunction in response to the instruction for executing the function,transmitting, to the electronic device, a control signal correspondingto user input received via the second user interface; and executing, bythe electronic device, an operation related to the function in responseto the control signal, wherein the operation is executed in cooperationwith the external device.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, functions, and advantages of the presentdisclosure will be more apparent from the following detailed descriptiontaken in conjunction with the accompanying drawings, in which:

FIG. 1 is a diagram of an example of a network environment that includesan electronic device, according to various embodiments of the presentdisclosure;

FIG. 2 is a block diagram of an example of an electronic device,according to various embodiments of the present disclosure;

FIG. 3 is a block diagram of an example of a program module, accordingto various embodiments of the present disclosure;

FIG. 4 is a diagram of an example of an electronic device, according tovarious embodiments of the present disclosure;

FIG. 5 is a diagram of an example of a system, according to variousembodiments of the present disclosure;

FIG. 6 is a sequence diagram of an example of a process, according tovarious embodiments of the present disclosure;

FIG. 7 is a diagram illustrating an example of the operation of asystem, according to various embodiments of the present disclosure;

FIG. 8 is a diagram illustrating an example of the operation of asystem, according to various embodiments of the present disclosure;

FIG. 9 is a diagram illustrating an example of the operation of asystem, according to various embodiments of the present disclosure;

FIG. 10 is a diagram illustrating an example of the operation of asystem, according to various embodiments of the present disclosure;

FIG. 11 is a flowchart of an example of a process, according to variousembodiments of the present disclosure;

FIG. 12 is a flowchart of an example of a process, according to variousembodiments of the present disclosure; and

FIG. 13 is a flowchart of an example of a process, according to variousembodiments of the present disclosure.

DETAILED DESCRIPTION

Hereinafter, various embodiments of the present disclosure will bedescribed with reference to the accompanying drawings. However, itshould be understood that there is no intent to limit the presentdisclosure to the particular forms disclosed herein; rather, the presentdisclosure should be construed to cover various modifications,equivalents, and/or alternatives of embodiments of the presentdisclosure. In describing the drawings, similar reference numerals maybe used to designate similar constituent elements.

As used herein, the expression “have”, “may have”, “include”, or “mayinclude” refers to the existence of a corresponding feature (e.g.,numeral, function, operation, or constituent element such as component),and does not exclude one or more additional features.

In the present disclosure, the expression “A or B”, “at least one of Aor/and B”, or “one or more of A or/and B” may include all possiblecombinations of the items listed. For example, the expression “A or B”,“at least one of A and B”, or “at least one of A or B” refers to all of(1) including at least one A, (2) including at least one B, or (3)including all of at least one A and at least one B.

The expression “a first”, “a second”, “the first”, or “the second” usedin various embodiments of the present disclosure may modify variouscomponents regardless of the order and/or the importance but does notlimit the corresponding components. For example, a first user device anda second user device indicate different user devices although both ofthem are user devices. For example, a first element may be termed asecond element, and similarly, a second element may be termed a firstelement without departing from the scope of the present disclosure.

It should be understood that when an element (e.g., first element) isreferred to as being (operatively or communicatively) “connected,” or“coupled,” to another element (e.g., second element), it may be directlyconnected or coupled directly to the other element or any other element(e.g., third element) may be interposed between them. In contrast, itmay be understood that when an element (e.g., first element) is referredto as being “directly connected,” or “directly coupled” to anotherelement (second element), there are no element (e.g., third element)interposed between them.

The expression “configured to” used in the present disclosure may beexchanged with, for example, “suitable for”, “having the capacity to”,“designed to”, “adapted to”, “made to”, or “capable of” according to thesituation. The term “configured to” may not necessarily imply“specifically designed to” in hardware. Alternatively, in somesituations, the expression “device configured to” may mean that thedevice, together with other devices or components, “is able to”. Forexample, the phrase “processor adapted (or configured) to perform A, B,and C” may mean a dedicated processor (e.g. embedded processor) only forperforming the corresponding operations or a generic-purpose processor(e.g., central processing unit (CPU) or application processor (AP)) thatcan perform the corresponding operations by executing one or moresoftware programs stored in a memory device.

The terms used in the present disclosure are only used to describespecific embodiments, and are not intended to limit the presentdisclosure. As used herein, singular forms may include plural forms aswell unless the context clearly indicates otherwise. Unless definedotherwise, all terms used herein, including technical and scientificterms, have the same meaning as those commonly understood by a personskilled in the art to which the present disclosure pertains. Such termsas those defined in a generally used dictionary may be interpreted tohave the meanings equal to the contextual meanings in the relevant fieldof art, and are not to be interpreted to have ideal or excessivelyformal meanings unless clearly defined in the present disclosure. Insome cases, even the term defined in the present disclosure should notbe interpreted to exclude embodiments of the present disclosure.

An electronic device according to various embodiments of the presentdisclosure may include at least one of, for example, a smart phone, atablet Personal Computer (PC), a mobile phone, a video phone, anelectronic book reader (e-book reader), a desktop PC, a laptop PC, anetbook computer, a workstation, a server, a Personal Digital Assistant(PDA), a Portable Multimedia Player (PMP), a MPEG-1 audio layer-3 (MP3)player, a mobile medical device, a camera, and a wearable device.According to various embodiments, the wearable device may include atleast one of an accessory type (e.g., a watch, a ring, a bracelet, ananklet, a necklace, a glasses, a contact lens, or a Head-Mounted Device(HMD)), a fabric or clothing integrated type (e.g., an electronicclothing), a body-mounted type (e.g., a skin pad, or tattoo), and abio-implantable type (e.g., an implantable circuit).

According to some embodiments, the electronic device may be a homeappliance. The home appliance may include at least one of, for example,a television, a Digital Video Disk (DVD) player, an audio, arefrigerator, an air conditioner, a vacuum cleaner, an oven, a microwaveoven, a washing machine, an air cleaner, a set-top box, a homeautomation control panel, a security control panel, a TV box (e.g.,Samsung HomeSync™, Apple TV™, or Google TV™), a game console (e.g.,Xbox™ and PlayStation™), an electronic dictionary, an electronic key, acamcorder, and an electronic photo frame.

According to another embodiment, the electronic device may include atleast one of various medical devices (e.g., various portable medicalmeasuring devices (a blood glucose monitoring device, a heart ratemonitoring device, a blood pressure measuring device, a body temperaturemeasuring device, etc.), a Magnetic Resonance Angiography (MRA), aMagnetic Resonance Imaging (MRI), a Computed Tomography (CT) machine,and an ultrasonic machine), a navigation device, a Global PositioningSystem (GPS) receiver, an Event Data Recorder (EDR), a Flight DataRecorder (FDR), a Vehicle Infotainment Devices, an electronic devicesfor a ship (e.g., a navigation device for a ship, and a gyro-compass),avionics, security devices, an automotive head unit, a robot for home orindustry, an automatic teller's machine (ATM) in banks, point of sales(POS) in a shop, or internet device of things (e.g., a light bulb,various sensors, electric or gas meter, a sprinkler device, a firealarm, a thermostat, a streetlamp, a toaster, a sporting goods, a hotwater tank, a heater, a boiler, etc.).

According to some embodiments, the electronic device may include atleast one of a part of furniture or a building/structure, an electronicboard, an electronic signature receiving device, a projector, andvarious kinds of measuring instruments (e.g., a water meter, an electricmeter, a gas meter, and a radio-wave meter). The electronic deviceaccording to various embodiments of the present disclosure may be acombination of one or more of the aforementioned various devices. Theelectronic device according to some embodiments of the presentdisclosure may be a flexible device. Further, the electronic deviceaccording to an embodiment of the present disclosure is not limited tothe aforementioned devices, and may include a new electronic deviceaccording to the development of technology.

Hereinafter, an electronic device according to various embodiments willbe described with reference to the accompanying drawings. As usedherein, the term “user” may indicate a person who uses an electronicdevice or a device (e.g., an artificial intelligence electronic device)that uses an electronic device.

FIG. 1 is a diagram of an example of a network environment that includesan electronic device, according to various embodiments.

An electronic device 101 within a network environment 100, according tovarious embodiments, will be described with reference to FIG. 1. Theelectronic device 101 may include a bus 110, a processor 120, a memory130, an input/output interface 150, a display 160, and a communicationinterface 170. According to an embodiment of the present disclosure, theelectronic device 101 may omit at least one of the above components ormay further include other components.

The bus 110 may include, for example, a circuit which interconnects thecomponents 110 to 170 and delivers a communication (e.g., a controlmessage and/or data) between the components 110 to 170.

The processor 120 may include any suitable type of processing circuitry,such as one or more general-purpose processors (e.g., ARM-basedprocessors), a Digital Signal Processor (DSP), a Programmable LogicDevice (PLD), an Application-Specific Integrated Circuit (ASIC), aField-Programmable Gate Array (FPGA), etc. For example, the processor120 may include one or more of a Central Processing Unit (CPU), anApplication Processor (AP), and a Communication Processor (CP). Theprocessor 120 may carry out, for example, calculation or data processingrelating to control and/or communication of at least one other componentof the electronic device 101.

The memory 130 may include any suitable type of volatile or non-volatilememory, such as Random-access Memory (RAM), Read-Only Memory (ROM),Network Accessible Storage (NAS), cloud storage, a Solid State Drive(SSD), etc. For example, the memory 130 may include a volatile memoryand/or a non-volatile memory. The memory 130 may store, for example,commands or data relevant to at least one other component of theelectronic device 101. According to an embodiment of the presentdisclosure, the memory 130 may store software and/or a program 140. Theprogram 140 may include, for example, a kernel 141, middleware 143, anApplication Programming Interface (API) 145, and/or application programs(or “applications”) 147. At least some of the kernel 141, the middleware143, and the API 145 may be referred to as an Operating System (OS).

The kernel 141 may control or manage system resources (e.g., the bus110, the processor 120, or the memory 130) used for performing anoperation or function implemented in the other programs (e.g., themiddleware 143, the API 145, or the application programs 147).Furthermore, the kernel 141 may provide an interface through which themiddleware 143, the API 145, or the application programs 147 may accessthe individual components of the electronic device 101 to control ormanage the system resources.

The middleware 143, for example, may serve as an intermediary forallowing the API 145 or the application programs 147 to communicate withthe kernel 141 to exchange data.

Also, the middleware 143 may process one or more task requests receivedfrom the application programs 147 according to priorities thereof. Forexample, the middleware 143 may assign priorities for using the systemresources (e.g., the bus 110, the processor 120, the memory 130, or thelike) of the electronic device 101, to at least one of the applicationprograms 147. For example, the middleware 143 may perform scheduling orloading balancing on the one or more task requests by processing the oneor more task requests according to the priorities assigned thereto.

The API 145 is an interface through which the applications 147 controlfunctions provided by the kernel 141 or the middleware 143, and mayinclude, for example, at least one interface or function (e.g.,instruction) for file control, window control, image processing,character control, and the like.

The input/output interface 150, for example, may function as aninterface that may transfer commands or data input from a user oranother external device to the other element(s) of the electronic device101. Furthermore, the input/output interface 150 may output the commandsor data received from the other element(s) of the electronic device 101to the user or another external device.

Examples of the display 160 may include a Liquid Crystal Display (LCD),a Light-Emitting Diode (LED) display, an Organic Light-Emitting Diode(OLED) display, a MicroElectroMechanical Systems (MEMS) display, and anelectronic paper display. The display 160 may display, for example,various types of contents (e.g., text, images, videos, icons, orsymbols) to users. The display 160 may include a touch screen, and mayreceive, for example, a touch, gesture, proximity, or hovering inputusing an electronic pen or a user's body part.

The communication interface 170 may establish communication, forexample, between the electronic device 101 and an external device (e.g.,a first external electronic device 102, a second external electronicdevice 104, or a server 106). For example, the communication interface170 may be connected to a network 162 through wireless or wiredcommunication, and may communicate with an external device (e.g., thesecond external electronic device 104 or the server 106). The wirelesscommunication may use at least one of, for example, Long Term Evolution(LTE), LTE-Advance (LTE-A), Code Division Multiple Access (CDMA),Wideband CDMA (WCDMA), Universal Mobile Telecommunications System(UMTS), Wireless Broadband (WiBro), and Global System for MobileCommunications (GSM), as a cellular communication protocol. In addition,the wireless communication may include, for example, short-rangecommunication 164. The short-range communication 164 may include atleast one of, for example, Wi-Fi, Bluetooth, Near Field Communication(NFC), and Global Navigation Satellite System (GNSS). GNSS may include,for example, at least one of global positioning system (GPS), globalnavigation satellite system (Glonass), Beidou Navigation satellitesystem (Beidou) or Galileo, and the European global satellite-basednavigation system, based on a location, a bandwidth, or the like.Hereinafter, in the present disclosure, the “GPS” may be interchangeablyused with the “GNSS”. The wired communication may include, for example,at least one of a Universal Serial Bus (USB), a High DefinitionMultimedia Interface (HDMI), Recommended Standard 232 (RS-232), and aPlain Old Telephone Service (POTS). The network 162 may include at leastone of a telecommunication network such as a computer network (e.g., aLAN or a WAN), the Internet, and a telephone network.

Each of the first and second external electronic devices 102 and 104 maybe of a type identical to or different from that of the electronicdevice 101. According to an embodiment of the present disclosure, theserver 106 may include a group of one or more servers. According tovarious embodiments of the present disclosure, all or some of theoperations performed in the electronic device 101 may be executed inanother electronic device or a plurality of electronic devices (e.g.,the electronic devices 102 and 104 or the server 106). According to anembodiment of the present disclosure, when the electronic device 101 hasto perform some functions or services automatically or in response to arequest, the electronic device 101 may request another device (e.g., theelectronic device 102 or 104 or the server 106) to execute at least somefunctions relating thereto instead of or in addition to autonomouslyperforming the functions or services. Another electronic device (e.g.,the electronic device 102 or 104, or the server 106) may execute therequested functions or the additional functions, and may deliver aresult of the execution to the electronic device 101. The electronicdevice 101 may process the received result as it is or additionally, andmay provide the requested functions or services. To this end, forexample, cloud computing, distributed computing, or client-servercomputing technologies may be used.

FIG. 2 is a block diagram of an example of an electronic device,according to various embodiments of the present disclosure.

The electronic device 201 may include, for example, all or a part of theelectronic device 101 shown in FIG. 1. The electronic device 201 mayinclude one or more processors 210 (e.g., Application Processors (AP)),a communication module 220, a Subscriber Identification Module (SIM)224, a memory 230, a sensor module 240, an input device 250, a display260, an interface 270, an audio module 280, a camera module 291, a powermanagement module 295, a battery 296, an indicator 297, and a motor 298.

The processor 210 may control a plurality of hardware or softwarecomponents connected to the processor 210 by driving an operating systemor an application program, and perform processing of various pieces ofdata and calculations. The processor 210 may be embodied as, forexample, a System on Chip (SoC). According to an embodiment of thepresent disclosure, the processor 210 may further include a GraphicProcessing Unit (GPU) and/or an image signal processor. The processor210 may include at least some (for example, a cellular module 221) ofthe components illustrated in FIG. 2. The processor 210 may load, intovolatile memory, commands or data received from at least one (e.g., anon-volatile memory) of the other components and may process the loadedcommands or data, and may store various data in a non-volatile memory.

The communication module 220 may have a configuration equal or similarto that of the communication interface 170 of FIG. 1. The communicationmodule 220 may include, for example, a cellular module 221, a Wi-Fimodule 223, a BT module 225, a GNSS module 227 (e.g., a GPS module 227,a Glonass module, a Beidou module, or a Galileo module), an NFC module228, and a Radio Frequency (RF) module 229.

The cellular module 221, for example, may provide a voice call, a videocall, a text message service, or an Internet service through acommunication network. According to an embodiment of the presentdisclosure, the cellular module 221 may distinguish and authenticate theelectronic device 201 in a communication network using the subscriberidentification module 224 (for example, the SIM card). According to anembodiment of the present disclosure, the cellular module 221 mayperform at least some of the functions that the AP 210 may provide.According to an embodiment of the present disclosure, the cellularmodule 221 may include a communication processor (CP).

For example, each of the Wi-Fi module 223, the BT module 225, the GNSSmodule 227, and the NFC module 228 may include a processor forprocessing data transmitted/received through a corresponding module.According to an embodiment of the present disclosure, at least some(e.g., two or more) of the cellular module 221, the Wi-Fi module 223,the BT module 225, the GNSS module 227, and the NFC module 228 may beincluded in one Integrated Chip (IC) or IC package.

The RF module 229, for example, may transmit/receive a communicationsignal (e.g., an RF signal). The RF module 229 may include, for example,a transceiver, a Power Amplifier Module (PAM), a frequency filter, a LowNoise Amplifier (LNA), and an antenna. According to another embodimentof the present disclosure, at least one of the cellular module 221, theWIFI module 223, the BT module 225, the GNSS module 227, and the NFCmodule 228 may transmit/receive an RF signal through a separate RFmodule.

The subscriber identification module 224 may include, for example, acard including a subscriber identity module and/or an embedded SIM, andmay contain unique identification information (e.g., an IntegratedCircuit Card Identifier (ICCID)) or subscriber information (e.g., anInternational Mobile Subscriber Identity (IMSI)).

The memory 230 (e.g., the memory 130) may include, for example, anembedded memory 232 or an external memory 234. The embedded memory 232may include at least one of a volatile memory (e.g., a Dynamic RandomAccess Memory (DRAM), a Static RAM (SRAM), a Synchronous Dynamic RAM(SDRAM), and the like) and a non-volatile memory (e.g., a One TimeProgrammable Read Only Memory (OTPROM), a Programmable ROM (PROM), anErasable and Programmable ROM (EPROM), an Electrically Erasable andProgrammable ROM (EEPROM), a mask ROM, a flash ROM, a flash memory(e.g., a NAND flash memory or a NOR flash memory), a hard disc drive, aSolid State Drive (SSD), and the like).

The external memory 234 may further include a flash drive, for example,a Compact Flash (CF), a Secure Digital (SD), a Micro Secure Digital(Micro-SD), a Mini Secure Digital (Mini-SD), an eXtreme Digital (xD), aMultiMediaCard (MMC), a memory stick, or the like. The external memory234 may be functionally and/or physically connected to the electronicdevice 201 through various interfaces.

The sensor module 240, for example, may measure a physical quantity ordetect an operation state of the electronic device 201, and may convertthe measured or detected information into an electrical signal. Thesensor module 240 may include, for example, at least one of a gesturesensor 240A, a gyro sensor 240B, an atmospheric pressure sensor(barometer) 240C, a magnetic sensor 240D, an acceleration sensor 240E, agrip sensor 240F, a proximity sensor 240G, a color sensor 240H (e.g.,red, green, and blue (RGB) sensor), a biometric sensor (medical sensor)2401, a temperature/humidity sensor 240J, an illuminance sensor 240K,and a Ultra Violet (UV) sensor 240M. Additionally or alternatively, thesensor module 240 may include, for example, an E-nose sensor, anelectromyography (EMG) sensor, an electroencephalogram (EEG) sensor, anelectrocardiogram (ECG) sensor, an Infrared (IR) sensor, an iris scansensor, and/or a finger scan sensor. The sensor module 240 may furtherinclude a control circuit for controlling one or more sensors includedtherein. According to an embodiment of the present disclosure, theelectronic device 201 may further include a processor configured tocontrol the sensor module 240, as a part of the processor 210 orseparately from the processor 210, and may control the sensor module 240while the processor 210 is in a sleep state.

The input device 250 may include, for example, a touch panel 252, a(digital) pen sensor 254, a key 256, or an ultrasonic input device 258.The touch panel 252 may use, for example, at least one of a capacitivetype, a resistive type, an infrared type, and an ultrasonic type. Thetouch panel 252 may further include a control circuit. The touch panel252 may further include a tactile layer, and provide a tactile reactionto the user.

The (digital) pen sensor 254 may include, for example, a recognitionsheet which is a part of the touch panel or is separated from the touchpanel. The key 256 may include, for example, a physical button, anoptical key or a keypad. The ultrasonic input device 258 may detect,through a microphone (e.g., the microphone 288), ultrasonic wavesgenerated by an input tool, and identify data corresponding to thedetected ultrasonic waves.

The display 260 (e.g., the display 160) may include a panel 262, ahologram device 264, or a projector 266. The panel 262 may include aconfiguration identical or similar to the display 160 illustrated inFIG. 1. The panel 262 may be implemented to be, for example, flexible,transparent, or wearable. The panel 262 may be embodied as a singlemodule with the touch panel 252. The hologram device 264 may show athree-dimensional (3D) image in the air by using an interference oflight. The projector 266 may project light onto a screen to display animage. The screen may be located, for example, in the interior of or onthe exterior of the electronic device 201. According to an embodiment ofthe present disclosure, the display 260 may further include a controlcircuit for controlling the panel 262, the hologram device 264, or theprojector 266.

The interface 270 may include, for example, a High-Definition MultimediaInterface (HDMI) 272, a Universal Serial Bus (USB) 274, an opticalinterface 276, or a D-subminiature (D-sub) 278. The interface 270 may beincluded in, for example, the communication interface 170 illustrated inFIG. 1. Additionally or alternatively, the interface 270 may include,for example, a Mobile High-definition Link (MHL) interface, a SecureDigital (SD) card/Multi-Media Card (MMC) interface, or an Infrared DataAssociation (IrDA) standard interface.

The audio module 280, for example, may bilaterally convert a sound andan electrical signal. At least some components of the audio module 280may be included in, for example, the input/output interface 150illustrated in FIG. 1. The audio module 280 may process voiceinformation input or output through, for example, a speaker 282, areceiver 284, earphones 286, or the microphone 288.

The camera module 291 is, for example, a device which may photograph astill image and a video. According to an embodiment of the presentdisclosure, the camera module 291 may include one or more image sensors(e.g., a front sensor or a back sensor), a lens, an Image SignalProcessor (ISP) or a flash (e.g., LED or xenon lamp).

The power management module 295 may manage, for example, the powersupply of the electronic device 201. According to an embodiment of thepresent disclosure, the power management module 295 may include a PowerManagement Integrated Circuit (PMIC), a charger Integrated Circuit (IC),or a battery or fuel gauge. The PMIC may use a wired and/or wirelesscharging method. Examples of the wireless charging method may include,for example, a magnetic resonance method, a magnetic induction method,an electromagnetic wave method, and the like. Additional circuits (e.g.,a coil loop, a resonance circuit, a rectifier, etc.) for wirelesscharging may be further included. The battery gauge may measure, forexample, remaining life battery 296, and voltage, current, ortemperature while charging. The battery 296 may include, for example, arechargeable battery and/or a solar battery.

The indicator 297 may display a particular state (e.g., a booting state,a message state, a charging state, or the like) of the electronic device201 or a part (e.g., the processor 210) of the electronic device 201.The motor 298 may convert an electrical signal into a mechanicalvibration, and may generate a vibration, a haptic effect, or the like.Although not illustrated, the electronic device 201 may include aprocessing device (e.g., a GPU) for supporting a mobile TV. Theprocessing device for supporting a mobile TV may process, for example,media data according to a certain standard such as Digital MultimediaBroadcasting (DMB), Digital Video Broadcasting (DVB), or mediaFLO™.

Each of the above-described component elements of hardware according tothe present disclosure may be configured with one or more components,and the names of the corresponding component elements may vary based onthe type of electronic device. In various embodiments, the electronicdevice may include at least one of the above-described elements. Some ofthe above-described elements may be omitted from the electronic device,or the electronic device may further include additional elements. Also,some of the hardware components according to various embodiments may becombined into one entity, which may perform functions identical to thoseof the relevant components before the combination.

FIG. 3 is a block diagram of an example of a program module, accordingto various embodiments of the present disclosure.

According to an embodiment of the present disclosure, the program module310 (e.g., the program 140) may include an Operating System (OS) forcontrolling resources related to the electronic device (e.g., theelectronic device 101) and/or various applications (e.g., theapplication programs 147) executed in the operating system. Theoperating system may be, for example, Android, iOS, Windows, Symbian,Tizen, Bada, or the like.

The program module 310 may include a kernel 320, middleware 330, an API360, and/or applications 370. At least some of the program module 310may be preloaded on an electronic device, or may be downloaded from anexternal electronic device (e.g., the electronic device 102 or 104, orthe server 106).

The kernel 320 (e.g., the kernel 141) may include, for example, a systemresource manager 321 and/or a device driver 323. The system resourcemanager 321 may control, allocate, or collect system resources.According to an embodiment of the present disclosure, the systemresource manager 321 may include a process management unit, a memorymanagement unit, a file system management unit, and the like. The devicedriver 323 may include, for example, a display driver, a camera driver,a Bluetooth driver, a shared memory driver, a USB driver, a keypaddriver, a Wi-Fi driver, an audio driver, or an Inter-ProcessCommunication (IPC) driver.

For example, the middleware 330 may provide a function required incommon by the applications 370, or may provide various functions to theapplications 370 through the API 360 so as to enable the applications370 to efficiently use the limited system resources in the electronicdevice. According to an embodiment of the present disclosure, themiddleware 330 (e.g., the middleware 143) may include at least one of arun time library 335, an application manager 341, a window manager 342,a multimedia manager 343, a resource manager 344, a power manager 345, adatabase manager 346, a package manager 347, a connectivity manager 348,a notification manager 349, a location manager 350, a graphic manager351, and a security manager 352.

The runtime library 335 may include a library module that a compileruses in order to add a new function through a programming language whilean application 370 is being executed. The runtime library 335 mayperform input/output management, memory management, the functionalityfor an arithmetic function, or the like.

The application manager 341 may manage, for example, a life cycle of atleast one of the applications 370. The window manager 342 may manageGraphical User Interface (GUI) resources used by a screen. Themultimedia manager 343 may recognize a format required for reproductionof various media files, and may perform encoding or decoding of a mediafile by using a codec suitable for the corresponding format. Theresource manager 344 may manage resources of a source code, a memory,and a storage space of at least one of the applications 370.

The power manager 345 may operate together with, for example, a BasicInput/Output System (BIOS) or the like to manage a battery or powersource and may provide power information or the like required for theoperations of the electronic device. The database manager 346 maygenerate, search for, and/or change a database to be used by at leastone of the applications 370. The package manager 347 may manageinstallation or an update of an application distributed in a form of apackage file.

For example, the connectivity manager 348 may manage wirelessconnectivity such as Wi-Fi or Bluetooth. The notification manager 349may display or notify of an event such as an arrival message, promise,proximity notification, and the like in such a way that does not disturba user. The location manager 350 may manage location information of anelectronic device. The graphic manager 351 may manage a graphic effectwhich will be provided to a user, or a user interface related to thegraphic effect. The security manager 352 may provide all securityfunctions required for system security, user authentication, or thelike. According to an embodiment of the present disclosure, when theelectronic device (e.g., the electronic device 101) has a telephone callfunction, the middleware 330 may further include a telephony manager formanaging a voice call function or a video call function of theelectronic device.

The middleware 330 may include a middleware module that forms acombination of various functions of the above-described components. Themiddleware 330 may provide a module specialized for each type of OS inorder to provide a differentiated function. Further, the middleware 330may dynamically remove some of the existing components or add newcomponents.

The API 360 (e.g., the API 145) is, for example, a set of APIprogramming functions, and may be provided with a differentconfiguration according to an OS. For example, in the case of Android oriOS, one API set may be provided for each platform. In the case ofTizen, two or more API sets may be provided for each platform.

The applications 370 (e.g., the application programs 147) may include,for example, one or more applications which may provide functions suchas a home 371, a dialer 372, an SMS/MMS 373, an Instant Message (IM)374, a browser 375, a camera 376, an alarm 377, contacts 378, a voicedial 379, an email 380, a calendar 381, a media player 382, an album383, a clock 384, health care (e.g., measuring exercise quantity orblood sugar), or environment information (e.g., providing atmosphericpressure, humidity, or temperature information).

According to an embodiment of the present disclosure, the applications370 may include an application (hereinafter, referred to as an“information exchange application” for convenience of description) thatsupports exchanging information between the electronic device (e.g., theelectronic device 101) and an external electronic device (e.g., theelectronic device 102 or 104). The information exchange application mayinclude, for example, a notification relay application for transferringspecific information to an external electronic device or a devicemanagement application for managing an external electronic device.

For example, the notification relay application may include a functionof transferring, to the external electronic device (e.g., the electronicdevice 102 or 104), notification information generated from otherapplications of the electronic device 101 (e.g., an SMS/MMS application,an e-mail application, a health management application, or anenvironmental information application). Further, the notification relayapplication may receive notification information from, for example, anexternal electronic device and provide the received notificationinformation to a user.

The device management application may manage (e.g., install, delete, orupdate), for example, at least one function of an external electronicdevice (e.g., the electronic device 102 or 104) communicating with theelectronic device (e.g., a function of turning on/off the externalelectronic device itself (or some components) or a function of adjustingthe brightness (or a resolution) of the display), applications operatingin the external electronic device, and services provided by the externalelectronic device (e.g., a call service or a message service).

According to an embodiment of the present disclosure, the applications370 may include applications (e.g., a health care application of amobile medical appliance or the like) designated according to anexternal electronic device (e.g., attributes of the electronic device102 or 104). According to an embodiment of the present disclosure, theapplications 370 may include an application received from an externalelectronic device (e.g., the server 106, or the electronic device 102 or104). According to an embodiment of the present disclosure, theapplications 370 may include a preloaded application or a third partyapplication that may be downloaded from a server. The names of thecomponents of the program module 310 of the illustrated embodiment ofthe present disclosure may change according to the type of operatingsystem.

According to various embodiments, at least a part of the programmingmodule 310 may be implemented in software, firmware, hardware, or acombination of two or more thereof. At least some of the program module310 may be implemented (e.g., executed) by, for example, the processor(e.g., the processor 1410). At least some of the program module 310 mayinclude, for example, a module, a program, a routine, a set ofinstructions, and/or a process for performing one or more functions.

The term “module” as used herein may, for example, mean a unit includingone of hardware, software, and firmware or a combination of two or moreof them. The “module” may be interchangeably used with, for example, theterm “unit”, “logic”, “logical block”, “component”, or “circuit”. The“module” may be a minimum unit of an integrated component element or apart thereof. The “module” may be a minimum unit for performing one ormore functions or a part thereof. The “module” may be mechanically orelectronically implemented. For example, the “module” according to thepresent disclosure may include at least one of an Application-SpecificIntegrated Circuit (ASIC) chip, a Field-Programmable Gate Arrays (FPGA),and a programmable-logic device for performing operations which havebeen known or are to be developed hereinafter.

According to various embodiments, at least some of the devices (forexample, modules or functions thereof) or the method (for example,operations) according to the present disclosure may be implemented by acommand stored in a computer-readable storage medium in a programmingmodule form. The instruction, when executed by a processor (e.g., theprocessor 120), may cause the one or more processors to execute thefunction corresponding to the instruction. The computer-readablerecording media may be, for example, the memory 130.

The computer readable recording medium may include a hard disk, a floppydisk, magnetic media (e.g., a magnetic tape), optical media (e.g., aCompact Disc Read-Only Memory (CD-ROM) and a Digital Versatile Disc(DVD)), magneto-optical media (e.g., a floptical disk), a hardwaredevice (e.g., a Read Only Memory (ROM), a Random Access Memory (RAM), aflash memory), and the like. In addition, the program instructions mayinclude high-class language codes, which can be executed by using aninterpreter, as well as machine codes made by a compiler. Theaforementioned hardware device may be configured to operate as one ormore software modules in order to perform the operation of the presentdisclosure, and vice versa.

Any of the modules or programming modules according to variousembodiments of the present disclosure may include at least one of theabove-described elements, exclude some of the elements, or furtherinclude other additional elements. The operations performed by themodules, programming module, or other elements according to variousembodiments of the present disclosure may be executed in a sequential,parallel, repetitive, or heuristic manner. Further, some operations maybe executed according to another order or may be omitted, or otheroperations may be added.

Various embodiments disclosed herein are provided merely to easilydescribe technical details of the present disclosure and to help theunderstanding of the present disclosure, and are not intended to limitthe scope of the present disclosure. Therefore, it should be construedthat all modifications and changes or modified and changed forms basedon the technical idea of the present disclosure fall within the scope ofthe present disclosure.

Various proposed embodiments of the present disclosure relate to amethod for operating a plurality of electronic devices by theinterworking and an electronic device that supports the same. Accordingto various embodiments of the present disclosure, the electronic devicemay be connected with various external electronic devices (e.g., thewearable device). The electronic device may be connected to, ordisconnected from, other external devices (e.g., the device) while theelectronic device is connected with the wearable device. In variousembodiments of the present disclosure, the electronic device may detectan event by the connection of the device or an event by thedisconnection of the device. In various embodiments of the presentdisclosure, the event by the connection of the device may include anoperation or an event (e.g., a pairing event) by which the device isconnected to enable the communication. In various embodiments of thepresent disclosure, the event by the disconnection of the device mayinclude an operation or an event (a pairing release event) in which thedevice, which has been connected to be able to communicate, isdisconnected.

In the following description, the event (e.g., the pairing event)according to the connection may be used as a term that includes anoperation or an event, which occurs according to the operation in whichthe electronic device and the device are connected with (access) eachother so that they can communicate with each other. The event (e.g., thepairing release event) according to the disconnection may be used as aterm that includes an operation or an event, which occurs according tothe operation in which the connection (access) of the electronic deviceand the wearable device are released so that they cannot communicatewith each other.

According to various embodiments of the present disclosure, theelectronic device may perform the operation that is related to thecorresponding event by interworking with the wearable device that isconnected with the electronic device in response to the pairing event orthe pairing release event by the device. According to an embodiment, theelectronic device may determine an execution method of a function thatcorresponds to the event in which a specific device is connected ordisconnected, and, based on the result of the determination operation,may execute a function for the corresponding event by interworking withthe wearable device or may execute the same solely (independently).

In the various embodiments of the present disclosure described below,the electronic device, the wearable device, and the device are separatedfor convenience of explanation, and the description will be made of theoperation in which a function corresponding to the device may beexecuted by the interworking between the electronic device and thewearable device according to the connection or the disconnection of thedevice with respect to the electronic device while the electronic deviceand the wearable device are connected. However, in various embodimentsof the present disclosure, the wearable device and the device may belongto the category of the electronic device, and the interworking operationbetween the electronic devices may be made in various electronic devicesas well as the wearable device and the device. For example, in variousembodiments of the present disclosure, the electronic device may includeall devices, such as all information communication devices, multimediadevices, wearable devices, or application devices thereof, which supportthe function according to various embodiments of the present disclosureand use one or more of various processors (for example, the processor120 or 210), such as an AP (application processor), a CP (communicationprocessor), a GPU (Graphic Processing Unit), or a CPU (centralprocessing unit).

In various embodiments of the present disclosure, the electronic deviceand the wearable device may be connected through a communicationinterface, and the electronic device may control the wearable devicethat is connected through the communication interface or may becontrolled by the wearable device. In various embodiments of the presentdisclosure, although the electronic device and the wearable device arerepresentatively described to be wirelessly connected by a wirelesscommunication interface that uses wireless network technology, such as apersonal area network (PAN), the electronic device and the wearabledevice may be connected via a wired communication interface that uses aUSB (Universal Serial Bus), a data connector, FireWire, i.Link, or thelike. In various embodiments of the present disclosure, the personalarea network may represent a network for the communication betweenvarious electronic devices (e.g., the wearable device, or otherelectronic devices) within a communication range of the electronicdevice, based on short-range communication technology. The short-rangecommunication technology may use at least one of WiFi (WirelessFidelity), Bluetooth, NFC (near field communication), IrDA (infrareddata association), UWB (ultra wideband), ZigBee, an RFID (radiofrequency identification), or the like.

In various embodiments of the present disclosure, the electronic deviceand the wearable device may be connected through a communicationinterface, and the electronic device may detect a pairing event in whichthe device is connected to enable the communication through acommunication interface or a pairing release event in which the deviceis disconnected to then be disabled from communicating. In variousembodiments of the present disclosure, the electronic device and thedevice may be connected in a variety of ways depending on the type ofdevice. According to an embodiment, the electronic device and the devicemay be wirelessly connected by a wireless communication interface thatuses wireless network technology, such as a personal area network, ormay be connected via a wired communication interface that uses a USB, adata connector, Firewire, i.link, or the like.

Hereinafter, a method, an apparatus, and a system of performing afunction according to the interworking between the electronic devices byusing an electronic device, a wearable device that is connected to theelectronic device, and a device that is connected to, or disconnectedfrom, the electronic device will be described. However, variousembodiments of the present disclosure may not be limited to thedescriptions provided below and thus, it should be construed that thepresent disclosure may be applied to various embodiments based on theembodiment provided below.

Hereinafter, various embodiments of the present disclosure will bedescribed from the perspective of hardware. However, various embodimentsof the present disclosure include a technology that uses both hardwareand software and thus, the various embodiments of the present disclosuremay not exclude the perspective of software.

FIG. 4 is a diagram of an example of an electronic device, according tovarious embodiments of the present disclosure.

Referring to FIG. 4, the electronic device 400, according to variousembodiments of the present disclosure, may include a wirelesscommunication unit 410, a user input unit 420, a touch screen 430, anaudio processing unit 440, a memory 450, an interface unit 460, a cameramodule 470, a controller 480, and a power supply unit 490. In variousembodiments of the present disclosure, the elements that are illustratedin FIG. 4 are not essential for the electronic device 400, so theelectronic device 400 may have more elements than FIG. 4, or may excludesome of the elements.

The wireless communication unit 410 may have the same or similarconfiguration as the communication module 220 of FIG. 2. The wirelesscommunication unit 410 may include one or more modules that enable thewireless communication between the electronic device 400 and a wirelesscommunication system, or between the electronic device 400 and otherelectronic devices (e.g., the electronic device 102 or 104, or theserver 106). For example, the wireless communication unit 410 may beconfigured to include a mobile communication module 411, a WLAN(wireless local area network) module 413, a short-range communicationmodule 415, a location calculating module 417, and a broadcast receivingmodule 419. In various embodiments of the present disclosure, thewireless communication unit 410 may perform wireless communication withthe wearable device on the basis of a configured communication scheme.

The mobile communication module 411 may transmit/receive wirelesssignals to/from at least one of a base station, external electronicdevices (e.g., the electronic device 104), or a variety of servers(e.g., an integration server, a provider server, a content server, aninternet server, a cloud server, or the like) through a mobilecommunication network. The wireless signals may include various types ofpieces of data according to a voice call signal, a video call signal, orthe transmission and reception of text/multimedia messages.

The mobile communication module 411 may receive one or more pieces ofdata (e.g., content, messages, e-mails, images, videos, weatherinformation, location information, time information, or the like).According to an embodiment, the mobile communication module 411 may beconnected with one or more other electronic devices (e.g., theelectronic device 104 or the server 106), which are connected with theelectronic device 400 through a network (e.g., the mobile communicationnetwork) in order to thereby obtain (receive) a variety of data. Themobile communication module 411 may transmit a variety of data, which isnecessary for the operation of the electronic device 400, to the outside(e.g., the server 106 or another electronic device 104) in response to auser's request.

The mobile communication module 411 may perform a communicationfunction. For example, the mobile communication module 411 may transforman RF (radio frequency) signal into a baseband signal to then beprovided to the controller 480, or may transform the baseband signalreceived from the controller 480 into an RF signal to then betransmitted, under the control of the controller 480. Here, thecontroller 480 may process the baseband signal based on variouscommunication schemes. For example, the communication schemes mayinclude a GSM (global system for mobile communication) communicationscheme, an EDGE (enhanced data GSM environment) communication scheme, aCDMA (code division multiple access) communication scheme, a W-CDMA(w-code division multiple access) communication scheme, an LTE (longterm evolution) communication scheme, or an OFDMA (orthogonal frequencydivision multiple access) communication scheme, but the communicationschemes are not limited thereto.

The WLAN module 413 may refer to a module to form a wireless LAN linkbetween a wireless Internet access and other electronic devices (e.g.,the electronic device 102 or the server 106). The WLAN module 413 may beprovided inside or outside the electronic device 400. The wirelessInternet technology may use a wireless LAN (WiFi, wireless fidelity),WiBro (wireless broadband), WiMax (world interoperability for microwaveaccess), HSDPA (High-Speed Downlink Packet Access), or mmWave(millimeter wave).

The WLAN module 413 may transmit one or more pieces of data selected bythe user to the outside, or may receive the same from the outside.According to an embodiment, the WLAN module 413 may interwork with atleast one of another electronic device (for example, the wearabledevice) or a server, which is connected to the electronic device 400through a network (e.g., the wireless Internet network) in order tothereby transmit a variety of data of the electronic device 400 to theoutside (e.g., the wearable device, another electronic device, orserver), or in order to thereby receive the same from the outside. TheWLAN module 413 may be normally maintained to be in the on-state, or maybe turned on according to the configuration of the electronic device 400or a user input.

The short-range communication module 415 may represent a module thatperforms short-range communication. The short-range communicationtechnology may use Bluetooth, low power Bluetooth (BLE), an RFID (RadioFrequency Identification), infrared data association (IrDA), UWB (UltraWideband), ZigBee, or NFC (near field communication).

The short-range communication module 415 may receive one or more piecesof data. According to an embodiment, the short-range communicationmodule 415 may interwork with other electronic devices (for example, thewearable device or the device), which are connected with the electronicdevice 400 through a network (e.g., the short-range communicationnetwork), in order to thereby transmit or receive a variety of data ofthe electronic device 400 to or from other electronic devices. Theshort-range communication module 415 may be normally maintained to be inthe on-state, or may be turned on according to the configuration of theelectronic device 400 or a user input.

The location calculating module 417 refers to a module for obtaining thelocation of the electronic device 400, and may include a GPS (globalposition system) module as a typical example. The location calculatingmodule 415 may measure the location of the electronic device 400 byusing a triangulation method. For example, the location calculatingmodule 417 may calculate distance information from three or more basestations and time information, and may calculate current locationinformation in three dimensions according to latitude, longitude, andaltitude by applying triangulation to the calculated information.Alternatively, the location calculating module 417 may continue toreceive the location information of the electronic device 400 from threeor more satellites in real time in order to thereby calculate thelocation information. The location information of the electronic device400 may be obtained in various manners.

The broadcast receiving module 419 may receive broadcast signals (e.g.,a TV broadcast signal, a radio broadcast signal, a data broadcastsignal, or the like) and/or broadcast-related information (e.g.,broadcast channels, broadcast programs, or information on a broadcastservice provider) from an external broadcast management server through abroadcast channel (e.g., a satellite broadcast channel, a terrestrialbroadcast channel, or the like).

The user input unit 420 may create input data for controlling theoperation of the electronic device 400 in response to a user input. Theuser input unit 420 may include one or more input means for detectingvarious user inputs. For example, the user input unit 420 may include akeypad, a dome switch, physical buttons, a touch pad (apressure-sensitive/capacitive type), a jog & shuttle, sensors (e.g., thesensor module 240), or the like.

Some of the user input unit 420 may be implemented as buttons on theoutside of the electronic device 400, and some or all of the user inputunit 420 may be implemented as a touch panel. The user input unit 420may receive a user input for initiating the operation of the electronicdevice 400, according to various embodiments of the present disclosure,and may generate an input signal according to the user input. Forexample, the user input unit 420 may receive various user inputs toperform a connection of the wearable device, photographing images, theexecution of applications, the data input (writing or inserting), theposture change of the electronic device 400, the display of content, thetransmission or reception of data, or the like, and may generate inputsignals according to the user inputs.

The touch screen 430 may represent input and output means for performingan input function and a displaying function at the same time, and mayinclude a display 431 (e.g., the display 160 or 260) and a touchdetecting unit 433. The touch screen 430 may: provide an input/outputinterface between the electronic device 400 and the user; transfer auser's touch input to the electronic device 400; or play an intermediaryrole to display the output from the electronic device 400 to the user.The touch screen 430 may provide the user with a visual output. Thevisual output may be formed of text, graphics, videos, or a combinationthereof. For example, in the embodiment of the present disclosure, thetouch screen 430 may display various screens according to the operationof the electronic device 400 through the display 431. The variousscreens, for example, may include various user interface (UI)-basedscreens that can be displayed to correspond to the executedapplications, such as, a messenger screen, a phone call screen, a gamescreen, a video reproduction screen, a gallery screen, a web pagescreen, a home screen, or a network connection screen.

The touch screen 430 may detect one or more events (e.g., a touch event,a hovering event, or an air gesture event), which are based at least oneof a touch, hovering, or an air gesture of the user through the touchdetecting unit 433 while a specific screen is displayed on the display431, and may transfer an input signal according to the event to thecontroller 480. The controller 480 may identify the transferred events,and may control the operation corresponding to the identified event.

According to various embodiments of the present disclosure, the display431 may display (output) a variety of information that is processed inthe electronic device 400. For example, the display 431 may display auser interface (UI) or a graphic user interface (GUI), which is relatedto a phone call, while the electronic device 400 is in a phone callmode. In addition, the display 431 may display a UI or a GUI, which isrelated to photographed and/or received images and the correspondingmode operation while the electronic device 400 is in a video call modeor in a photographing mode. The display 431 may display data or content,which is related to the usage of the electronic device 400, orinformation on other electronic devices (e.g., the wearable device orthe device), which are connected to the network. The display 431 maydisplay various application execution screens corresponding to theexecuted applications.

The display 431 may support the display in a horizontal mode or thedisplay in a vertical mode according to the rotation direction (or lyingdirection) of the electronic device 400, or the display according to theswitch between the horizontal mode and the vertical mode. The display431 may use various displays (e.g., the display 160). Some displays maybe implemented as a transparent display that is configured to be atransparent type or an optical transparent type.

The touch detecting unit 433 may be placed on the display 431, and maydetect a user input that touches or approaches the surface of the touchscreen 430. The user input may include a touch event or a proximityevent, which is input based on at least one of a single-touch, amulti-touch, hovering, or an air gesture. For example, the user inputmay be input by tapping, dragging, sweeping, flicking, drag & drop, ordrawing gestures (e.g., handwriting). The touch detecting unit 433 maydetect a user input (e.g., the touch event or the proximity event) onthe surface of the touch screen 430, and may generate a signalcorresponding to the detected user input to then be transmitted to thecontroller 480. The controller 480 may control the function executioncorresponding to the area where the user input (e.g., the touch event orthe proximity event) occurs by a signal transmitted by the touchdetecting unit 433.

In various embodiments of the present disclosure, the touch detectingunit 433 may receive a user input for initiating an operation related tothe use of the electronic device 400, and may generate an input signalaccording to the user input. The touch detecting unit 433 may beconfigured to convert a change in the pressure that is applied to aspecific portion of the display 431 or a capacitance that occurs in aspecific portion of the display 431 into an electric input signal. Thetouch detecting unit 433 may detect the position and the area where theinput means (e.g., user's fingers, an electronic pen, or the like) touchor approach the surface of the display 431. In addition, the touchdetecting unit 433 may be implemented to detect the pressure of thetouch according to the type of applied touch as well. If the touchdetecting unit 433 receives a touch or a proximity input, the signal(s)corresponding thereto may be transmitted to a touch screen controller(not shown). The touch screen controller (not shown) may process thesignal(s), and then may transfer corresponding data to the controller480. Thus, the controller 480 may identify the area where the touch orproximity has occurred on the touch screen 430, and may execute afunction corresponding thereto.

The audio processing unit 440 may have the same or similar configurationas the audio module 280 of FIG. 2. The audio processing unit 440 mayperform a function of transmitting audio signals received from thecontroller 480 to a speaker (SPK) 441 and transmitting audio signals,such as voice, received from a microphone (MIC) 443 to the controller480. The audio processing unit 440 may convert voice/sound data into anaudible sound to then be output through the speaker 441 according to thecontrol of the controller 480, and may convert an audio signal, such asvoice, received from the microphone 443 into a digital signal to then bedelivered to the controller 480. The audio processing unit 440 mayoutput an audio signal in response to a user input according to audioprocessing information (e.g., sound effects, music files, etc.)contained in the data.

The speaker 441 may output audio data that is received from the wirelesscommunication unit 410 or is stored in the memory 450. The speaker 441may output an audio signal that is related to various operations(functions), which are executed in the electronic device 400. Thespeaker 441 may play the role of making an output of an audio stream,such as voice recognition, voice replication, digital recording, or aphone call function. Although it is not shown in the various embodimentsof the present disclosure, the speaker 441 may include earphones,headphones, or a headset, which are attachable and detachable, and maybe connected with the electronic device 400 through an external port.

The microphone 443 may receive external sound signals to process thesame into electrical voice data. The voice data processed through themicrophone 443 may be converted into a form that can be transmitted tothe outside through the mobile communication module 411 while theelectronic device 400 is in a phone call mode. The microphone 443 may beimplemented to have a variety of noise reduction algorithms for removingnoise that is generated in the course of receiving the external soundsignal. The microphone 443 may play the role of making an input of anaudio stream, such as a voice instruction (e.g., a voice instruction forinitiating the connection operation of the electronic device 400 and thewearable device), voice recognition, digital recording, or a phone callfunction. For example, the microphone 443 may convert sound signals intoelectrical signals. According to various embodiments of the presentdisclosure, the microphone 443 may include an internal microphone thatis built in the electronic device 400 and an external microphone that isconnected to the electronic device 400.

The memory 450 (e.g., the memory 130 or 230) may store one or moreprograms that are executed by the controller 480, and may perform afunction of temporarily storing the input/output data. The input/outputdata may include, for example, content, messenger data (e.g., chatdata), contact information (e.g., the wired or wireless phone number),messages, media files (e.g., audio files, video files, images file,etc.), or the like.

The memory 450 may store one or more programs and data, which arerelated to the execution of a function by the interworking between theelectronic device 400 and the wearable device according to an event(e.g., the pairing event or the pairing release event), which is createdby the device. For example, in various embodiments of the presentdisclosure, the memory 450 may store one or more programs that performthe operations of: detecting the connection or disconnection of thedevice; determining the type of device that is connected ordisconnected; identifying a user interface related to a wearable devicethat matches the determined device; determining an execution method of afunction corresponding to an event that is detected according to whetheror not the user interface exists; and displaying the user interfacebased on the result of the determination operation and solely executingthe corresponding function, or transmitting a function-executinginstruction (a user interface executing instruction) to the wearabledevice and executing the function by interworking with the wearabledevice, and the data that is processed according thereto.

The memory 450 may store the frequency of use (e.g., the frequency ofthe wearable device connection, the frequency of using the device, thefrequency of the device connection, the frequency of using theapplication, the frequency of using content, or the like), theimportance, and the priority according to the operation of theelectronic device 400 as well. The memory 450 may store data onvibrations and sounds in various patterns, which are output in responseto a touch input or a proximity input on the touch screen 430. Thememory 450 may continuously or temporarily store an operating system(OS) of the electronic device 400, programs that are related to theinput and the display control by using the touch screen 430, programsthat are related to the control of various operations (functions) of theelectronic device 400, and a variety of data that is generated by theoperation of each program.

The memory 450 (e.g., the memory 130 or 230) may include an extendedmemory (e.g., the external memory 234) or an internal memory (e.g., theinternal memory 232). The electronic device 400 may operate inassociation with a web storage that performs a storage function of thememory 450 on the internet.

The memory 450 may store a variety of software. For example, thesoftware components may include an operating system software module, acommunication software module, a graphic software module, a userinterface software module, an MPEG (Moving Picture Experts Group)module, a camera software module, or one or more application softwaremodules. In addition, the module, which is a software component, may beexpressed as a group of instructions, so the module may be referred toas a set of instructions. The module may be expressed as a program aswell. In various embodiments of the present disclosure, the memory 450may include additional modules (instructions) in addition to the modulesdescribed above. Alternatively, if necessary, some of the modules(instructions) may not be used.

The operating system software module may include a plurality of softwarecomponents to control the general system operation. The control of thegeneral system operation, for example, may refer to the management andcontrol of the memory, the management and control of storage hardware(the device), and the management and control of power. In addition, theoperating system software module may perform a function to facilitatecommunication between a variety of hardware (devices) and softwarecomponents (modules) as well.

The communication software module may enable the communication withother electronic devices, such as a wearable device, a device, acomputer, a server, or a mobile terminal, through the wirelesscommunication unit 410 or the interface unit 460. In addition, thecommunication software module may be configured as a protocol structurecorresponding to its communication scheme.

The graphic software module may include a number of software componentsfor providing and displaying graphics on the touch screen 430. The term“graphics” may be used to have a meaning that includes text, web pages,icons, digital images, videos, animations, or the like.

The user interface software module may include various softwarecomponents that are related to the user interface (UI). For example, theuser interface software module may include the change status of the userinterface or a condition on which the status of the user interface ischanged.

The MPEG module may include software components that enable digitalcontent-related (e.g., video related or audio related) processes andfunctions (e.g., the creation, reproduction, distribution, andtransmission of the content).

The camera software module may include camera-related softwarecomponents that enable the camera-related processes and functions.

The application modules may include a web browser containing a renderingengine, e-mail, instant messaging, word processing, keyboard emulation,an address book, a touch list, widget, digital right management (DRM),voice recognition, a position determining function, location-basedservices, or the like. According to various embodiments of thedisclosure, the application module may include instructions forconfiguring the connection with the wearable device. For example, theapplication module may provide an event that is related to the devicewhile the electronic device 400 is connected to the wearable device, andmay allow the electronic device 400 and the wearable device to interworkwith each other to perform the function in response to the event.

The interface unit 460 may have the same or similar configuration as theinterface 270 of FIG. 2. The interface unit 460 may play the role of aninterface with respect to all of external other electronic devicesconnected to the electronic device 400. The interface unit 460 may:receive data from the external other electronic devices; receive powerto transfer the same to the elements of the electronic device 400; orallow the data in the electronic device 400 to be transmitted toexternal other electronic devices. For example, the interface unit 460may include a wired/wireless headset port, an external charger port, awired/wireless data port, a memory card port, a port to be connected toa device that adopts an identification module, audio input/output ports,video input/output ports, an earphone port, or the like. According tovarious embodiments of the present disclosure, the interface unit 460may communicate with the device in order to thereby exchange a varietyof data (e.g., a control signal by a device, a response signal by theelectronic device 400, a video signal, an audio signal, files, or thelike) while the electronic device 400 and the device are connected witheach other for communication.

The camera module 470 (e.g., the camera module 291) represents aconfiguration that supports a photographing function of the electronicdevice 400. The camera module 470 is able to support the photographingof images (still images or moving images) for an object. The cameramodule 470 may photograph a certain object and may transmit thephotographed data to the display 431 and the controller 480, under thecontrol of the controller 480. The camera module 470 may be configuredto include an image sensor (or a camera sensor) (not shown), whichconverts an optical input signal into an electric signal, and an imagesignal processor (not shown), which converts the electric signalreceived from the image sensor into digital image data. The image sensormay include a sensor that uses a CCD (charge coupled device) or a CMOS(complementary metal-oxide-semiconductor). Additionally oralternatively, the camera module 470, for example, may include a colorsensor that senses the wavelength of light radiated or reflected by anobject to identify colors. The camera module 470 may support an imageprocessing function for supporting the shooting according to a varietyof shooting options (for example, zooming, aspect ratio, effects (e.g.,sketch, mono, sepia, vintage, mosaic, frame, etc.)) by the configurationof the user.

The controller 480 may control the overall operation of the electronicdevice 400. For example, the controller 480 may perform the controlrelated to voice communication, data communication, or videocommunication. The controller 480 may include one or more processors(e.g., the processor 210), or may be referred to as a processor. Forexample, the controller 480 may include, as separate elements, acommunications processor (CP), an application processor (AP), aninterface {e.g., GPIO (general purpose input/output)}, or an internalmemory, or the elements may be integrated into one or more integratedcircuits. The application processor may execute various softwareprograms to perform a number of functions for the electronic device 400,and the communication processor may perform the processing and controlfor voice communication and data communication. In addition, thecontroller 480 may execute a specific software module (a set ofinstructions) stored in the memory 450 in order to thereby perform avariety of functions corresponding to the specific module.

According to various embodiments of the present disclosure, thecontroller 480 may control the interworking between the electronicdevices (e.g., the electronic device 400, the wearable device, or thedevice) and the operation of performing various functions according tothe interworking. For example, the controller 480 may configure theconnection between the electronic device 400 and the wearable device.The controller 480 may detect events generated by the device while theelectronic device 400 is connected to the wearable device. For example,the controller 480 may detect a pairing event corresponding to theconnection of the device or a pairing release event corresponding to thedisconnection of the device. The controller 480 may determine the typeof device to be connected or disconnected in response to detecting theevent due to the device, and may identify a function or a dedicated userinterface, which is related to the wearable device that matches thedetermined device.

According to various embodiments, the controller 480 may determine anexecution method of the function corresponding to the detected eventdepending on whether or not the function or the user interface exists.For example, if the function related to the wearable device that matchesthe device exists, the controller 480 may determine that the functioncorresponding to the event is to be executed by the interworking withthe wearable device. In addition, if the function related to thewearable device that matches the device does not exist, the controller480 may determine that the function corresponding to the event is to beexecuted solely (independently) by the electronic device 400.

According to various embodiments, the controller 480 may display a userinterface (e.g., the first user interface) based on the result of thedetermination operation, and may control the sole operation of thefunction by the electronic device 400. In addition, the controller 480may transmit a function-executing instruction (or a second userinterface executing instruction) to the wearable device based on theresult of the determination operation, and may control the functionoperation by the interworking with the wearable device.

According to various embodiments of the present disclosure, thecontroller 480 may: connect the wearable device based on wired orwireless communication; transmit, to the wearable device, functioncontrol instructions (e.g., a function-executing instruction or afunction-end instruction) corresponding to the event of the connectionto the electronic device through wired or wireless communication or thedisconnection therefrom; and control the related function execution inresponse to a user input (e.g., a gesture input) from the wearabledevice.

According to various embodiments of the present disclosure, thecontroller 480 may interwork with the software modules stored in thememory 450 in order to thereby perform the interworking functions of theelectronic device 400 described above, according to various embodiments.In addition, according to various embodiments of the present disclosure,the controller 480 may be implemented by one or more modules to processthe interworking functions of the electronic devices mentioned above. Inaddition, according to various embodiments of the present disclosure,the controller 480 may be implemented by one or more processors thatexecute one or more programs stored in the memory 450 in order tothereby control the operation (for example, the interworking of theelectronic device 400, the device 500, and the wearable device 600, anda function execution operation according to the interworking) of theelectronic device 400, according to various embodiments of the presentdisclosure.

The controller 480, according to various embodiments of the presentdisclosure, may control various operations related to normal functionsof the electronic device 400, as well as the functions above. Forexample, when a specific application is executed, the controller 480 maycontrol the operation and display of the application. In addition, thecontroller 480 may receive input signals corresponding to a variety oftouch event inputs or proximity event inputs, which are supported by thetouch-based or proximity-based input interface (e.g., the touch screen430), and may control the function operation according thereto. Inaddition, the controller 480 may control the transmission and receptionof a variety of data based on wired communication or wirelesscommunication.

The power supply unit 490, under the control of the controller 480, mayreceive power from an internal power source or an external power sourcein order to thereby supply the power necessary for the operation of eachelement. In various embodiments of the present disclosure, one or moreprocessors of the controller 480, the display 431, or the wirelesscommunication unit 410 may be powered on and off by the power supplyunit 490 under the control of the controller 480.

Various embodiments described in the present disclosure may beimplemented in a computer (or similar device)-readable recording mediumusing software, hardware or a combination thereof. According to thehardware implementation, the embodiments of the present disclosure maybe implemented using at least one of Application Specific IntegratedCircuits (ASICs), Digital Signal Processors (DSPs), Digital SignalProcessing Devices (DSPDs), Programmable Logic Devices (PLDs), FieldProgrammable Gate Arrays (FPGAs), processors, controllers,micro-controllers, microprocessors, and electrical units for performingother functions.

In various embodiments of the present disclosure, the recording mediummay include a computer-readable recording medium that records a programto execute the operations of: detecting an event in response to theconnection of a device while being connected to a wearable device;determining a user interface dedicated to the wearable device, whichmatches the device related to the event; determining a functionexecution method according to whether or not the user interface exists;and independently executing the function or executing the function byinterworking with the wearable device based on a result of thedetermination operation.

In some cases, the embodiments described herein may be implemented bythe controller 480 itself. Furthermore, according to the softwareimplementation, the embodiments such as procedures and functionsdescribed in the present specification may also be implemented asseparate software modules. The software modules may perform one or morefunctions and operations described in the present specification.

According to various embodiments of the present disclosure, at leastsome of the functions that are executed by the electronic device 400 maybe performed by the external device (e.g., the server 106 or thewearable device). For example, the server 106 may: include a processingmodule corresponding to the controller 480; process at least some of thefunctions related to the interworking between the electronic device 400and other electronic devices and the control of the function executionaccording thereto by using the processing module, based on at least someof the information transmitted from the electronic device 400; andtransmit the result thereof to the electronic device 400.

As described above, the electronic device 400, according to variousembodiments of the present disclosure, may include: a communication unit(e.g., the WLAN module 413, the short-range communication module 415,the interface unit 460, or the like) that performs the connection withthe wearable device 600 and the external device 500; and a processor(e.g., the controller 480) that is functionally connected with thecommunication unit and that detects an event that is related to theconnection of the external device 500 while being connected with thewearable device 600, determines a function that matches the externaldevice 500, which is related to the event, and transmits an executinginstruction for executing the function to the wearable device 600.

According to various embodiments, the communication unit may include acommunication module that supports a communication connection with thewearable device or the external device, respectively, based on wired orwireless communication. In various embodiments, the event includes anevent in which the electronic device is connected with the externaldevice to be communicable.

According to various embodiments, the wearable device may include adevice that is able to be connected with the electronic device through acommunication interface based on wired or wireless communication, andthe external device may include an electronic pen, earphones, a charger,a display device, or another electronic device, which can be connectedwith the electronic device through a communication interface based onwired or wireless communication.

According to various embodiments, the processor may control theexecution of the function that is related to a control signal receivedfrom the wearable device. According to various embodiments, theprocessor may determine whether or not a function of the wearabledevice, which matches the type of external device, exists, and if thefunction of the wearable device does not exist, may provide the wearabledevice with information by which a function, which can be executed bythe interworking with the device, may be obtained.

According to various embodiments, the processor may: determine whetheror not a function of the wearable device, which matches the type ofexternal device, exists; if the function of the wearable device exists,display the first user interface that is related to the function;transmit, to the wearable device, an executing instruction for thefunction or the second user interface that is related to the function;and execute an operation that is related to the function in response toa control signal of the wearable device based on the second userinterface.

According to various embodiments, the first user interface and thesecond user interface may include configurations that are related to thefunction, and the second user interface may be provided based on atleast some of the configurations that are implemented in the first userinterface. According to various embodiments, the processor may detect anevent by the disconnection of the external device while being connectedwith the wearable device, and to transmit an end instruction for endingthe function related to the event to the wearable device.

As described above, the electronic device 400, according to variousembodiments of the present disclosure, may include: a communication unit(e.g., the WLAN module 413, the short-range communication module 415,the interface unit 460, or the like) that performs the connection withother electronic devices (e.g., the wearable device 600 or the externaldevice 500); and a controller 480 that, while being connected with thefirst electronic device (e.g., the wearable device), detects an eventdue to the connection of the second electronic device (e.g., thedevice), determines a function that matches the second electronicdevice, which is related to the event, and transmits, to the firstelectronic device, an executing instruction for executing the functionin the first electronic device.

FIG. 5 is a diagram of an example of a system, according to variousembodiments of the present disclosure. As illustrated, the systemincludes an electronic device 400, a device 500, and a wearable device600.

As shown in FIG. 5, the electronic device 400, for example, may includeat least some of the elements of the electronic device shown in FIG. 4,and may be the same as, or different from, the electronic device 400 ofFIG. 4. In various embodiments of the present disclosure, the electronicdevice 400 may be connected with the wearable device 600 through acommunication interface (e.g., the WLAN module 413, the short-rangecommunication module 415, and the interface unit 460 of FIG. 4). Thecommunication interface may include at least one of a wiredcommunication interface and a wireless communication interface. Inaddition, the electronic device 400 may be connected with the device 500through communication interface (e.g., the WLAN module 413, theshort-range communication module 415, and the interface unit 460 of FIG.4).

The device 500 may be connected with the electronic device 400 through acommunication interface (e.g., a wired or wireless communicationinterface). In various embodiments of the present disclosure, the device500, for example, may include an electronic pen 510, earphones 520, acharger 530, a display device 540, or the other electronic device 550,but the device is not limited thereto and may include various types ofdevices that can be connected with the electronic device 400.

The wearable device 600 may be connected with the electronic device 400through a communication interface (e.g., a wired or wirelesscommunication interface). In various embodiments of the presentdisclosure, the wearable device 600 may represent a device that can beput on the body of the user. For example, the wearable device mayinclude a wrist-watch type of device that can be worn on the wrist or adevice in the form of glasses, which can be worn around the eyes, andmay represent a device that may provide a variety of functions byinterworking with the electronic device 400.

In various embodiments of the present disclosure, the wearable device600 may include a communication unit 610, a touch screen 620, and acontroller 630.

In various embodiments, the communication unit 610 of the wearabledevice 600 may include a communication interface for connecting to theelectronic device 400, and may transmit and receive data from theelectronic device 400 and the wearable device 600. In variousembodiments, the touch screen 620 of the wearable device 600 may includea component (e.g., a touch detecting unit) for receiving an input fromthe user, and may receive a touch or proximity type of input from theuser to then be transmitted to the controller 630. The touch screen 620may include a component (e.g., the display) for displayingoutput-related data transmitted from the controller 630 to the user. Invarious embodiments, the controller 630 of the wearable device 600 maycontrol the overall operations of the wearable device 600. For example,the controller 630 may control to transfer the data from the electronicdevice 400, which is received from the communication unit 610, to thetouch screen 620 to then display the same, or may include a componentfor generating a function control signal corresponding to the user inputreceived through the touch screen 620 and transmits the same to theelectronic device 400 through the communication unit 610.

In various embodiments of the present disclosure, the electronic device400 and the wearable device 600 may be connected to each other in awell-known manner. According to an embodiment, the electronic device 400may be connected with the wearable device 600 according to acommunication interface based on the wireless communication, such as theWLAN module 413 or the short-range communication module 415, or may beconnected with the wearable device 600 based on the wired communicationthrough the interface unit 460.

In various embodiments of the present disclosure, the electronic device400 may be connected to the device 500 in a well-known manner. Accordingto various embodiments, if the device 500 is an electronic pen 510, theelectronic pen 510 may be mounted (inserted) into a hole (not shown)provided in the electronic device 400. When the electronic pen 510 isremoved from the hole, the electronic device 400 may detect a pairingevent due to the electronic pen 510, and may be connected with theelectronic pen 510 in a well-known manner in order to therebycommunicate with the same (e.g., data communication). When theelectronic pen 510 is mounted (inserted) in the hole, the electronicdevice 400 may detect a pairing release event due to the electronic pen510, and the connection with the electronic pen 510 may be released in awell-known manner.

According to various embodiments of the present disclosure, if thedevice 500 is the earphones 520, the earphones 520 may be connected toan earphone connector (or port) (not shown) provided in the electronicdevice 400 through an earphone jack. When the earphones 520 areconnected to the earphone connector, the electronic device 400 maydetect a pairing event by the earphones 520 and begin communicating withthe earphones 520 in a well-known manner. When the earphones 520 aredetached (separated) from the earphone connector, the electronic device400 may detect a pairing release event due to the earphones 520, and theconnection with the earphones 520 may be released.

According to various embodiments, if the device 500 is the charger 530,the charger 530 may be connected to a data connector (or a chargingport) (not shown) provided in the electronic device 400 through a datacable. When the charger 530 is connected to the data connector, theelectronic device 400 may detect a pairing event due to the charger 530in order to thereby perform the communication (e.g., a chargingoperation) with the charger 530. When the charger 530 is detached(separated) from the data connector, the electronic device 400 maydetect a pairing release event due to the charger 530, and theconnection with the charger 530 may be released, thereby completing thecharging operation.

According to various embodiments, if the device 500 is the displaydevice 540, the display device 540 may be connected to the electronicdevice 400 via a USB or HDMI connection, or may be connected to theelectronic device 400 via a wireless connection (e.g., short-rangeconnection). When the display device 540 accesses the electronic device400 based on wired or wireless communication, the electronic device 400may detect a pairing event due to the display device 540, and may beconnected with the display device 540 in order to perform thecommunication (e.g., an external output or multi-screen operation, amirroring operation, or the like). When the connection with the displaydevice 540 is released, the electronic device 400 may detect a pairingrelease event due to the display device 540, and may be disconnectedfrom the display device 540.

According to various embodiments of the present disclosure, if thedevice 500 is the other electronic device 550, the other electronicdevice 550 may be connected to the electronic device 400 via a wired orwireless connection. When the other electronic device 550 is connectedto the electronic device 400 based on wired or wireless communication,the electronic device 400 may detect a pairing event due to the otherelectronic device 550, and may be connected with the other electronicdevice 550 to perform the communication (e.g., the data transmission andreception or a phone call operation). When the connection of the otherelectronic device 550 through wired or wireless communication isreleased, the electronic device 400 may detect a pairing release eventdue to the other electronic device 550 and may be disconnected from theother electronic device 550 to then end the related operation.

Referring to FIG. 5, according to various embodiments of the presentdisclosure, the electronic device 400 and the wearable device 600 may beconnected to each other. For example, the electronic device 400 and thewearable device 600 may perform a connecting operation (e.g., a pairingprocess) such that the electronic device 400 and the wearable device 600may interwork with each other through a communication scheme, such asWiFi-Direct, Bluetooth, NFC, or the like. The electronic device 400 andthe wearable device 600 may interwork with each other in accordance withthe execution of the connecting operation, and they may share with eachother data that is obtained in real-time.

When the electronic device 400 and the wearable device 600 are connectedwith each other, the controller 480 may detect events generated by thedevice 500. In various embodiments of the present disclosure, the eventsmay include a pairing event in which the device 500 is connected to theelectronic device 400 and a pairing release event in which the device500 is disconnected from the electronic device 400 to then be disabledfrom communicating. For example, the device 500 may be connected to theelectronic device 400 by using the communication interface, which issupported by the device 500, among a variety of communicationinterfaces, as described above. The controller 480 may detect when theelectronic device 400 is connected or disconnected from the device 500by using the event detecting unit 481. In various embodiments of thepresent disclosure, the event detecting unit 481 may detect the changestatus for the connection or disconnection of the device 500 in at leastone of a variety of communication interfaces that are available in theelectronic device 400.

According to various embodiments, the electronic device 400 may detectthe connection and disconnection of the device 500 while the electronicdevice 400 and the wearable device 600 interwork with each otheraccording to the completion of the connection (e.g., pairing) thereof.According to an embodiment, the electronic pen 510, which may bedisposed in the electronic device 400, may cause the electronic device400 to generate events when the electronic pen 510 is mounted (attached)on, or detached from, the electronic device 400.

When the controller 480 detects a pairing event associated with thedevice 500 through the event detecting unit 481, the controller 480 mayidentify a function that is associated with the device 500 and thewearable device 600 in response to the pairing event. The controller 480may display a user interface (e.g., the first user interface) related tothe identified function on the display 431 of the electronic device 400.The controller 480 may transmit, to the wearable device 600, afunction-executing instruction of the function and a user interface(e.g., the second user interface) related to the function in parallel tothe display operation of the user interface or in sequence with respectto the same.

Although the first user interface and the second user interface areseparately described in various embodiments of the present disclosure,the first user interface and the second user interface may refer todifferent versions of the same user interface that are available ondifferent devices (e.g., the electronic device 400, the wearable device600, and the device 500). The first user interface and the second userinterface may be separated according to whether the corresponding userinterface is implemented in the electronic device 400 or in the wearabledevice 600. For example, the display of the wearable device 600, whichdisplays the user interface, may be smaller than the display 431 of theelectronic device 400. Therefore, in various embodiments of the presentdisclosure, the second user interface may be implemented in a differentform from the first user interface so as to correspond to the displaysize of the wearable device 600. According to an embodiment, the seconduser interface may be reconfigured in a simplified form compared to thefirst user interface by selecting only a core component (e.g., a mainmenu) from among various components (e.g., menus) of the first userinterface, and then may be provided, as screen examples shown in thedrawings (e.g., FIG. 7, FIG. 8, or FIG. 9) described later. According toan embodiment, the first user interface and the second user interfacemay include components related to the functions above, and the seconduser interface may be implemented based on at least some of thecomponents that are implemented in the first user interface. Theelectronic device 400 may reconfigure the second user interface tocorrespond to the wearable device 600 based on the first user interface,and may provide the same.

In addition, in various embodiments of the present disclosure, the firstuser interface and the second user interface may be provided in adifferent form, respectively, according to the case where the electronicdevice 400 and the wearable device 600 independently execute thefunction without interlocking with each other or the case where theelectronic device 400 and the wearable device 600 interwork with eachother to execute the function.

According to various embodiments, when the event detecting unit 481detects that a connection with a connection with the device 500 isestablished or terminated, the controller 480 may perform a search inorder to detect whether or not a user interface {e.g., the second userinterface that can be implemented in the wearable device 600 (e.g., theuser interface dedicated to the wearable device 600)}, which matches thedetected devices 500, exists by the function processing unit 483. Forexample, if the device 500 is the electronic pen 510 and the function,which can be executed by the electronic pen 510, is drawing a picture, auser interface by which the user can draw a picture by using theelectronic pen 510 through the display 431 according to the function ofdrawing may be matched. The user interface may be divided into a portionfor directly drawing a picture and a portion that is related toadditional options {e.g., the component of a pen attribute (thickness,color, or the like)} necessary for the drawing.

In various embodiments of the present disclosure, in instances in whichthe electronic device 400 and the wearable device 600 are connected tointerlock with each other, the user interface may be divided to definethe first user interface that is implemented in the electronic device400 and the second user interface that is implemented in the wearabledevice 600.

According to various embodiments of the present disclosure, when thepairing event associated with the electronic pen 510 is detected by theevent detecting unit 481, the first user interface, which is comprisedof elements necessary for directly drawing a picture through the display431, may be implemented in the electronic device 400, and the seconduser interface, which is comprised of elements related to the additionaloptions necessary for the drawing, may be provided in the wearabledevice 600. According to various embodiments of the present disclosure,when the display device 540 is detected, a portion of a user interface(e.g., a function execution screen display portion), which is related tothe display of the executed function, may be implemented as the firstuser interface to then be provided by the electronic device 400, and aportion (e.g., a control portion for the execution screen display),which is related to the control of the executed function, may beimplemented as the second user interface to then be provided by thewearable device 600.

According to various embodiments, the controller 480 (e.g., the functionprocessing unit 483) may identify an available function by interworkingwith the wearable device 600 in response to the pairing event. If a userinterface (e.g., the second user interface) related to the identifiedfunction exist, the controller 480 (e.g., function processing unit 483)may transmit, to the wearable device 600, an instruction for executingthe function, and the wearable device 600 may display the second userinterface, which corresponds to the function, as a result of executingthe instruction.

According to various embodiments of the present disclosure, if a userinterface (e.g., the second user interface), which matches the wearabledevice 600 (which can be implemented in the wearable device 600) inrelation to the identified function, does not exist, or if no availablefunction exists in relation to the wearable device 600, the controller480 (e.g., the function processing unit 483) may allow the userinterface to be executed by the electronic device 400 regardless of thetype of user interface and may allow the electronic device to solely(independently) process the operation related to the correspondingfunction without the interworking.

According to various embodiments, if a user interface, which matches thewearable device 600 in relation to the identified function, does notexist, or if no available function exists in relation to the wearabledevice 600, the controller 480 (e.g., the function processing unit 483)may transmit a related function (e.g., an application) or a userinterface (e.g., the second user interface) from the electronic device400 or the device 500 to the wearable device 600, or may install thesame in the wearable device 600. According to an embodiment, ininstances in which the related function or the second user interface ispre-installed in the electronic device 400 or the device 500, therelated data may be transmitted to the wearable device 600 to controlthe installation. According to an embodiment, in instances in which therelated function or the second user interface is not pre-installed inthe electronic device 400 or the device 500, the controller may downloadthe related data from the related server (e.g., an application server, aweb server, etc.) to then be transmitted to the wearable device 600, ormay control the wearable device 600 to download and install the relateddata.

According to various embodiments, the wearable device 600 may receivethe function-executing instruction for the function execution and theexecution of the second user interface corresponding thereto from theelectronic device 400. When the function-executing instruction isreceived, the wearable device 600 may display information correspondingto the function-executing instruction, and may wait for the reception ofa user input (e.g., the first user input) (e.g., acceptance orrejection) corresponding thereto. If the wearable device 600 detects auser input indicating acceptance of the usage of the wearable device 600in relation to the function, the wearable device 600 may display andprovide the second user interface to the user. The user input, forexample, may include a posture change input of the wearable device 600,a biometric recognition input, a button input, or a touch gesture input.According to an embodiment, the user input may be made based on anoperation in which the user touches the touch screen 620 of the wearabledevice 600 or buttons (not shown) provided on the wearable device 600,or performs a gesture of changing (tilting) the posture of the wearabledevice 600 (e.g., a gesture of tiling a user's wrist in the case of awrist-watch type of device), or a gesture of watching the cameraprovided in the wearable device 600.

According to various embodiments, the wearable device 600 may receive auser input (e.g., the second user input) based on the second userinterface, and may transmit a functional control signal corresponding tothe user input to the electronic device 400. Then, the electronic device400 may receive the function control signal from the wearable device600, and in response to the function control signal, may perform afunction (operation) corresponding to the function control signal basedon the first user interface.

As described above, according to various embodiments of the presentdisclosure, when the electronic device 400 and the wearable device 600are connected with each other, the interworking function may beperformed in response to the pairing event of the device 500 through theevent detecting unit 481. According to various embodiments of thepresent disclosure, the controller 480 may detect the pairing releaseevent associated with the device 500 through the event detecting unit481 while performing the interworking function.

If the controller 480 detects the pairing release event associated withthe device 500, the controller 480 may selectively end the runninginterworking function with the wearable device 600 in response to thepairing release event. For example, the controller 480 may causewearable device 600 to end the function in progress and display of theuser interface (e.g., the second user interface), which is related tothe function. According to an embodiment, the controller 480 maytransmit, to the wearable device 600, a function-end instruction toterminate the function and the display of the user interface (e.g., thesecond user interface), which is related to the function.

According to various embodiments, the electronic device 400 may transmitthe function-end instruction (e.g., function termination instruction) tothe wearable device 600, and may solely process the function that hasbeen performed through the interworking with the wearable device 600.According to an embodiment, the electronic device 400 may convert thefirst user interface, which is being displayed, into a user interfacethat is integrated with the first user interface and the second userinterface to then be displayed.

According to various embodiments, the wearable device 600 may receive,from the electronic device 400, the function-end instruction for thefunction end and the display end of the second user interfacecorresponding thereto. When the wearable device 600 receives thefunction-end instruction, the wearable device 600 may terminate thefunction that is in progress by the interworking with the electronicdevice 400, and may end the display of the second user interface, inresponse to the function-end instruction.

Various embodiments of the present disclosure describe an example inwhich the interworking function may be executed according to the pairingevent associated with the device 500 while the electronic device 400 andthe wearable device 600 are connected with each other, and theinterworking function is terminated in the wearable device 600 accordingto the pairing release event associated with the device 500. However,various embodiments of the present disclosure are not limited thereto,and even with the pairing release event associated with the device 500,the interworking function between the electronic device 400 and thewearable device 600 may be maintained.

As described above, a system for the interworking between the electronicdevices, according to various embodiments of the present disclosure, mayinclude: a wearable device 600 that is connected with the electronicdevice 400 through a communication interface based on wired or wirelesscommunication, and transmits a control signal corresponding to the userinput to the electronic device 400; a device 500 that is connected withthe electronic device 400 through a communication interface based onwired or wireless communication and generates an event corresponding tothe connection with the electronic device 400 to enable thecommunication; and an electronic device that detects an event associatedwith the connection of the device 500 while being connected with thewearable device 600, determines a function that matches the device 500in response to the event, and transmits, to the wearable device 600, aninstruction for the execution of the function in the wearable device600.

FIG. 6 is a sequence diagram of an example of a process, according tovarious embodiments of the present disclosure.

Referring to FIG. 6, in operation 601, the electronic device 400 may beconnected to, or disconnected from the device 500 based on a givencommunication method, and in operation 603, the electronic device 400may detect a corresponding event (e.g., the pairing event or the pairingrelease event) in response to the connection or disconnection of thedevice 500.

According to various embodiments, the electronic device 400 may detect(and/or generate) a pairing event when the electronic pen 510 is removedfrom the electronic device 400, and may detect (and/or generate) apairing release event in response to the electronic pen 510 beingmounted on the electronic device 400. Additionally or alternatively, theelectronic device 400 may detect a pairing event in response to theconnection (the communication-enabled state) of the display device 540with the electronic device 400, and may detect a pairing release eventin response to the disconnection (the communication-disabled state) ofthe display device 540 from the electronic device 400.

In operation 605, in response to the event associated with the device500, the electronic device 400 may make a request to the wearable device600 for the execution of an operation according to the event. Accordingto various embodiments, the electronic device 400 may transmit, to thewearable device 600, an instruction to execute the correspondingfunction and display the user interface (e.g., the second userinterface) related to the function in response to the pairing event.Alternatively, the electronic device 400 may transmit, to the wearabledevice 600, a function-end instruction to terminate the correspondingfunction and the user interface (e.g., the second user interface)related thereto in response to the pairing release event.

In operation 607, the wearable device 600 may execute the relatedoperation in response to the operation execution request (e.g., thefunction-executing instruction or the function-end instruction) of theelectronic device 400. For example, the wearable device 600 may executethe related function and may display the second user interfacecorresponding thereto in response to the function-executing instruction.Additionally or alternatively, the wearable device 600 may end therelated function and the display of the second user interfacecorresponding thereto in response to the function-end instruction.According to an embodiment, the wearable device 600 may display abackground screen or may display a function execution screen that hasbeen previously displayed when the display of the second user interfaceis terminated.

In operation 609, the wearable device 600 may detect a user input.According to various embodiments of the present disclosure, it may beassumed that the user input of the operation 609 is an input forcontrolling the operation (function) related to the first user interfacethat is in progress in the electronic device 400 (and/or the device 500)while the second user interface is displayed. Thus, in instances inwhich the wearable device 600 ends the display of the second userinterface in response to the function-end instruction, the operation 609and the following operation 611 may be omitted.

In operation 611, a control signal corresponding to the detected userinput may be transmitted to the electronic device 400. For example, thewearable device 600 may receive a user input that is applied to thefirst user interface in progress in the electronic device 400 based onthe second user interface that is executed in response to thefunction-executing instruction, and may transmit a control signalaccording thereto to the electronic device 400.

In operation 613, the electronic device 400 may receive the controlsignal transmitted from the wearable device 600, and may execute therelated operation in response to the control signal. For example, theelectronic device 400 may apply the operation (function) correspondingto the control signal to the second user interface in progress to thendisplay the same. The related operation executed in response to thecontrol signal will be described in further detail with respect to FIGS.7-10 below.

FIG. 7 is a diagram illustrating an example of the operation of asystem, according to various embodiments of the present disclosure.

As shown in FIG. 7, FIG. 7 may show an example in which the electronicdevice 400 and the wearable device 600 are connected with each other,and the device 500 is the electronic pen 510. According to anembodiment, when the electronic pen 510 is detached from the electronicdevice 400, the electronic device 400 and the electronic pen 510 may bein a communicable state, and the electronic device 400 may detect apairing event in response to the removal of the electronic pen 510. Whenthe electronic device 400 detects the pairing event corresponding to theremoval of the electronic pen 510, the electronic device 400 may controlthe execution of the user interface of the wearable device 600 inresponse to the pairing event.

Referring to FIG. 7, the electronic pen 510 may be provided (accepted)in a receptacle that is formed in the main body of the electronic device400. According to various embodiments, the pairing event may occur inthe electronic device 400 according to the removal of the electronic pen510, and a function and a user interface, which match the electronic pen510, may be executed in response to the pairing event. According tovarious embodiments, although the example of FIG. 7 shows that thefunction matching the electronic pen 510 is an image editing functionand the user interface corresponding to the function is a user interfacerelated to the editing of the image, various embodiments are possible.For example, the electronic pen 510 may be associated with variousfunctions, such as drawing a picture, note-taking, or a gallery.

According to various embodiments, the electronic device 400 may detectthe removal of the electronic pen 510 while the application for editingan image is in progress, or may detect the removal of the electronic pen510 while another function is in progress or in the standby mode.According to various embodiments, the attachment/removal of theelectronic pen 510 in the electronic device 400 may be determined basedon sensed information. According to an embodiment, when the electronicpen 510 is attached to the electronic device 400, a sensing circuitrelated to the electronic pen 510 in the electronic device 400 mayopen-circuit. According to another embodiment, when the electronic pen510 is detached from the electronic device 400, the sensing circuitrelated to the electronic pen 510 in the electronic device 400 mayshort-circuit.

According to various embodiments, the electronic device 400 mayrecognize the attachment of the electronic pen 510 when the sensingcircuit is in the open state, and it may be defined as the communicationdisconnection with respect to the attachment of the electronic pen 510in the following description. According to various embodiments, theelectronic device 400 may recognize the removal of the electronic pen510 when the sensing circuit is in the short state, and it may bedefined as the communication connection with respect to the removal ofthe electronic pen 510 in the following description.

According to various embodiments, when an application is being executedby the electronic device 400, a user interface of the application (e.g.,an integrated user interface) may be displayed on the electronic device400, and a pairing event may occur in this state due to the electronicpen 510.

According to various embodiments, in response to detecting the pairingevent, the electronic device 400 may perform a search in order toidentify whether or not a user interface (e.g., the second userinterface 730) dedicated to the wearable device 600, which matches theelectronic pen 510, exists. For example, when the application forediting an image is in progress in the electronic device 400, a userinterface (e.g., the second user interface 730) for determining theattribute of a pen may exist in the wearable device 600, and theelectronic device 400 may identify whether or not a user interfacecorresponding thereto exists.

According to various embodiments, the electronic device 400 may convertthe user interface (e.g., the integrated user interface) related to theapplication, which is being displayed, into the first user interface 710to then be displayed concurrently with searching for the user interface(e.g., the second user interface 730) dedicated to the wearable device600 or in sequence with respect to the same.

According to various embodiments, a pairing event associated with theelectronic pen 510 may occur while the electronic device 400 executesanother function or is in the standby mode. According to variousembodiments, in response to detecting the pairing event, the electronicdevice 400 may perform an operation of converting the user interface,which is being displayed according to the execution of another function,into the first user interface 710 to then be displayed, or an operationof turning on the display 431 in the standby mode and displaying thefirst user interface 710 in parallel to the operation of searching forthe user interface (e.g., the second user interface 730) dedicated tothe wearable device 600, which matches the electronic pen 510, or insequence with respect to the same.

According to various embodiments, if the user interface (e.g., thesecond user interface 730) dedicated to the wearable device 600 exists,the electronic device 400 may transmit a function-executing instructionfor the execution of the second user interface 730 to the wearabledevice 600.

According to various embodiments, the wearable device 600 may receivethe function-executing instruction, and may wait for a user input.According to an embodiment, when the function-executing instruction isreceived, the wearable device 600 may output (e.g., displaying,vibration, alarm, etc.) information associated with thefunction-executing instruction (e.g., execution identifying informationof the second user interface 730), and may wait to receive the firstuser input (e.g., a configured gesture input corresponding to theacceptance or rejection, a physical button input for the acceptance orrejection, a software-based button input for the acceptance orrejection, or the like), which corresponds thereto. In variousembodiments of the present disclosure, the operation of waiting for thefirst user input may be omitted. For example, when the wearable device600 receives the function-executing instruction, the wearable device 600may directly execute and display the second user interface 730 inresponse to the function-executing instruction without waiting for thefirst user input.

In various embodiments of the present disclosure, the electronic device400 and the wearable device 600 may perform a data communicationoperation, such as a request for the related information (e.g., theattribute of a pen) necessary for the provision of the second userinterface 730 and the reception thereof in response to the first userinput or the direct execution of the second user interface 730.

According to various embodiments, if the execution of the second userinterface 730 is accepted by the user, the wearable device 600 mayexecute and display the second user interface 730 (e.g., a userinterface for determining the attribute of a pen). According to variousembodiments, in instances in which the second user interface 730 is inprogress by the interworking between the wearable device 600 and theelectronic device 400, the operation above may be omitted.

According to various embodiments, when the wearable device 600 receivesthe second user input from the user while the second user interface 730is displayed, the wearable device 600 may execute the related operation.According to an embodiment, when a specific attribute of a pen to beapplied to the first user interface 710 is selected through the seconduser interface 730, the wearable device 600 may transmit, to theelectronic device 400, a control signal to instruct the application tothe first user interface 710 based on the selected and specificattribute of a pen.

According to various embodiments, the electronic device 400 may applythe specific attribute of a pen to the first user interface 710 inresponse to the control signal and may display the same.

FIG. 8 is a diagram illustrating an example of the operation of asystem, according to various embodiments of the present disclosure.

As shown in the FIG. 8, FIG. 8 may show an example in which theelectronic device 400 and the wearable device 600 are connected witheach other, and the device 500 is the charger 530. According to anembodiment, when the charger 530 is connected (inserted) through a dataconnector of the electronic device 400, the electronic device 400 andthe charger 530 may be in a communicable state, and the electronicdevice 400 may detect a pairing event in response to the connection ofthe charger 530. When the electronic device 400 detects the pairingevent indicating that the charger 530 is connected to the electronicdevice 400, the electronic device 400 may control the execution of theuser interface of the wearable device 600 in response to the pairingevent.

Referring to FIG. 8, the event may occur in the electronic device 400 inresponse to the charger 530 being connected, and a function and a userinterface, which match the charger 530, may be executed in response tothe event. According to various embodiments, although the example ofFIG. 8 shows that the function matching the charger 530 is a chargingfunction and the user interface corresponding thereto is a userinterface related to the charging, various embodiments are possible.

According to various embodiments, the electronic device 400 may detectthe connection of the charger 530 while another function is in progressor in the standby mode. The electronic device 400 may detect a pairingevent in response to the connection of the charger 530.

According to various embodiments, in response to the pairing event, theelectronic device 400 may perform a search in order to identify whetheror not a user interface dedicated to the wearable device 600, whichmatches the charger 530, exists. For example, when the charging functionis in progress in the electronic device 400, a user interface (e.g., thesecond user interface 830) for providing an indication of chargingstatus may exist in the wearable device 600, and the electronic device400 may identify whether or not a user interface corresponding theretoexists.

According to various embodiments, the electronic device 400 may performan operation of converting the user interface, which is being displayedaccording to the execution of another function, into the first userinterface 810 related to the charging function to then be displayed, oran operation of turning on the display 431 in the standby mode anddisplaying the first user interface 810 related to the charging functionin parallel to the operation of searching for the user interface (e.g.,the second user interface 830) dedicated to the wearable device 600 orin sequence with respect to the same.

According to various embodiments, if the user interface (e.g., thesecond user interface 830) dedicated to the wearable device 600 exists,the electronic device 400 may transmit to the wearable device 600 afunction-executing instruction for executing the second user interface830.

According to various embodiments, the wearable device 600 may: receivethe function-executing instruction; output (e.g., displaying, vibration,alarm, etc.) the information on the function-executing instruction; andwait to receive the first user input for determining the execution ofthe second user interface 830 according to the function-executinginstruction. In various embodiments of the present disclosure, theoperation of waiting for the first user input may be omitted. Forexample, when the wearable device 600 receives the function-executinginstruction, the wearable device 600 may directly execute and displaythe second user interface 830 in response to the function-executinginstruction without waiting for the first user input.

In various embodiments of the present disclosure, the electronic device400 and the wearable device 600 may perform a data communicationoperation, such as a request for the related information (e.g., thecharging amount of a battery of the electronic device 400) necessary forthe provision of the second user interface 830 and the reception thereofin response to the first user input or the direct execution of thesecond user interface 830.

According to various embodiments, if the execution of the second userinterface 830 is accepted by the user, the wearable device 600 mayexecute and display the second user interface 830 (e.g., a userinterface capable of displaying the charging status). In variousembodiments, the wearable device 600 may display the current chargingstatus of the electronic device 400, or additionally or alternatively,may display the charging status of the electronic device 400 and thecharging status of the wearable device 600 together.

FIG. 9 is a diagram illustrating an example of the operation of asystem, according to various embodiments of the present disclosure.

More particularly, FIG. 9 shows an example in which the electronicdevice 400 and the wearable device 600 are connected with each other,and the device 500 is the display device 540. According to anembodiment, when the display device 540 is connected to the electronicdevice 400, the electronic device 400 and the display device 540 may bein a communicable state, and the electronic device 400 may detect apairing event in response to the connection with the display device 540being established.

When the electronic device 400 detects the pairing event indicating thatthe connection with the display device 540 is established, theelectronic device 400 may control the execution of the user interface ofthe wearable device 600 in response to the pairing event.

Referring to FIG. 9, the electronic device 400 may be connected with thedisplay device 540 through a screen transmitting function (e.g., amirroring function). According to various embodiments, a pairing eventmay occur in the electronic device 400 according to the connection ofthe display device 540, and a function and a user interface, which matchthe display device 540, may be executed in response to the pairingevent. According to various embodiments, although the example of FIG. 9shows that the function matching the display device 540 is areproduction-related control function and the user interfacecorresponding thereto is a user interface related to the control ofcontent (e.g., videos), which is reproduced, various embodiments arepossible.

According to various embodiments, the electronic device 400 may detectthat a connection is established with the display device 540 while theapplication for reproducing content is being executed or may detect theconnection of the display device 540 while another function is inprogress or in the standby mode.

According to various embodiments, when an application is in progress inthe electronic device 400, a user interface (e.g., an integrated userinterface), which is related to the application, may be displayed on theelectronic device 400, and the pairing event may occur in this state dueto the display device 540.

According to various embodiments, in response to the pairing event, theelectronic device 400 may perform a search in order to identify whetheror not a user interface (e.g., the second user interface 930) dedicatedto the wearable device 600, which matches the display device 540,exists. For example, when a media player is executed by the electronicdevice 400, a user interface (e.g., the second user interface 930) forperforming the video reproduction control or the volume control mayexist in the wearable device 600, and the electronic device 400 mayidentify whether or not a corresponding user interface exists.

According to various embodiments, the electronic device 400 may convertthe user interface (e.g., the integrated user interface), which isrelated to the displayed application, into the first user interface 910(e.g., that includes a reproduction control-related interface in FIG. 9)and displaying the same, and an operation of transmitting, to thedisplay device 540, the third user interface 950 (e.g., a videoreproduction screen without the control-related interface in FIG. 9) ofthe electronic device 400 according to a screen transmission function(e.g., the mirroring function) in parallel to the operation of searchingfor the user interface (e.g., the second user interface 930) dedicatedto the wearable device 600 or in sequence with respect to the same. Invarious embodiments of the present disclosure, the electronic device 400may provide a user interface (e.g., a user interface that does notcontain a reproduction control-related interface), which is the same orsimilar to the user interface (e.g., the third user interface 950)provided in the display device 540 instead of providing the first userinterface 910.

According to various embodiments, the pairing event associated with thedisplay device 540 may occur while the electronic device 400 executesanother function or is in the standby mode. According to variousembodiments, the electronic device 400, in response to detecting thepairing event, may: convert the user interface, which is being displayedaccording to the execution of another function, into the first userinterface 910 to then be displayed; or an operation of turning on thedisplay 431 in the standby mode and displaying the first user interface910; and an operation of displaying (e.g., the mirroring function) thethird user input 950 on the display device 540 in parallel to theoperation of searching for the user interface (e.g., the second userinterface 930) dedicated to the wearable device 600, which matches thedisplay device 540, or in sequence with respect to the same.

According to various embodiments, if the user interface (e.g., thesecond user interface 930) dedicated to the wearable device 600 exists,the electronic device 400 may transmit a function-executing instructionfor the execution of the second user interface 930 to the wearabledevice 600.

According to various embodiments, the wearable device 600 may receivethe function-executing instruction and may begin waiting for a userinput. According to an embodiment, when the wearable device 600 receivesthe function-executing instruction, the wearable device 600 may output(e.g., displaying, vibration, alarm, etc.) information associated withthe function-executing instruction (e.g., execution identifyinginformation on the second user interface 930), and may wait for thereception of the first user input corresponding thereto. In variousembodiments of the present disclosure, the operation of waiting for thefirst user input may be omitted. For example, when the wearable device600 receives the function-executing instruction, the wearable device 600may directly execute and display the second user interface 930 inresponse to the function-executing instruction without waiting for thefirst user input.

In various embodiments, the electronic device 400 and the wearabledevice 600 may perform a data communication operation, such as making arequest for the related information (e.g., a reproduction/volume-relatedfunction control signal) necessary for the provision of the second userinterface 930 and the reception thereof in response to the first userinput or the direct execution of the second user interface 930.

According to various embodiments, if the execution of the second userinterface 930 is accepted by the user, the wearable device 600 mayexecute and display the second user interface 930 (e.g., a userinterface capable of performing the video reproduction control or thevolume control). In various embodiments, in instances in which thesecond user interface 930 is in progress by the interworking between thewearable device 600 and the electronic device 400, the operation abovemay be omitted.

According to various embodiments, when the second user input is receivedwhile the second user interface 930 is displayed, the wearable device600 may execute the related operation. According to an embodiment, aspecific control function to control the first user interface 910 (orthe third user interface 950) is selected through the second userinterface 930, the wearable device 600 may transmit, to the electronicdevice 400, a control signal to instruct the application thereof to thefirst user interface 910 (or the third user interface 950) based on theselected specific control function.

According to various embodiments, the electronic device 400 may applythe specific control function to the first user interface 910 and thethird user interface 950 and may provide the same in response to thecontrol signal. According to an embodiment, the electronic device 400may control the volume of the video that is produced, or may fastforward or rewind the video.

FIG. 10 is a diagram illustrating an example of the operation of asystem, according to various embodiments of the present disclosure. Moreparticularly, FIG. 10 shows an example in which the electronic device400 and the wearable device 600 are connected with each other, and thedevice 500 is the other electronic device 550. According to anembodiment, when the other electronic device 550 is connected to theelectronic device 400, the electronic device 400 and the otherelectronic device 550 may be in a communicable state, and the electronicdevice 400 may detect a pairing event in response to the connection ofthe other electronic device 550. When the electronic device 400 detectsthe pairing event corresponding to the connection of the otherelectronic device 550, the electronic device 400 may control theexecution of the user interface of the wearable device 600 in responseto the pairing event.

Referring to FIG. 10, the connection of the electronic device 400 andthe other electronic device 550 for the transmission of content or filesmay be established wirelessly and/or over a wired medium. According tovarious embodiments, a pairing event may occur in the electronic device400 according to the connection of the other electronic device 550, anda function and a user interface, which match the other electronic device550, may be executed in response to the pairing event. According tovarious embodiments, although the example of FIG. 10 shows that thefunction matching the other electronic device 550 is a file transferfunction and the user interface corresponding thereto is a userinterface related to the operation of transferring the files, variousembodiments are possible.

According to various embodiments, the electronic device 400 may detectthe connection of the other electronic device 550 while a galleryapplication (e.g., an image viewer) is being executed or may detect theconnection of the other electronic device 550 while another function isin progress or in the standby mode.

According to various embodiments, when an application is in progress inthe electronic device 400, a user interface (e.g., the first userinterface 1010), which is related to the application, may be displayedin the electronic device 400, and the pairing event by the otherelectronic device 550 may occur in this state.

According to various embodiments, in response to the pairing event, theelectronic device 400 may perform a search in order to identify whetheror not a user interface (e.g., the second user interface 1030) (e.g., aclipboard application-related user interface) dedicated to the wearabledevice 600, which matches the other electronic device 550, exists. Forexample, when the file transfer function is in progress in theelectronic device 400, a user interface (e.g., the second user interface1030), which is related to the clipboard application that is configuredto temporarily store the transmitted files, may exist in the wearabledevice 600, and the electronic device 400 may identify whether or not auser interface corresponding thereto exists. The electronic device 400may further convert the user interface, which is related to thedisplayed application, into the first user interface 1010 and displayingthe same in parallel to the operation of searching for the userinterface (e.g., the second user interface 1030) that is dedicated tothe wearable device 600 or in sequence with respect to the same.

According to various embodiments, while the electronic device 400executes another function or is in the standby mode, the pairing eventby the other electronic device 550 may occur. According to variousembodiments, the electronic device 400, in response to detecting thepairing event, may convert the user interface, which is being displayedaccording to the execution of another function, into the first userinterface 1010 to then be displayed, or an operation of turning on thedisplay 431 in the standby mode and displaying the first user interface1010 concurrently with searching for the user interface (e.g., thesecond user interface 1030) dedicated to the wearable device 600, whichmatches the other electronic device 550, or in sequence with respect tothe same.

According to various embodiments, if the user interface (e.g., thesecond user interface 1030) dedicated to the wearable device 600 exists,the electronic device 400 may transmit a function-executing instructionfor the execution of the second user interface 1030 to the wearabledevice 600.

According to various embodiments, the wearable device 600 may receivethe function-executing instruction and may wait for a user input.According to an embodiment, when the wearable device 600 receives thefunction-executing instruction, the wearable device 600 may output(e.g., displaying, vibration, alarm, etc.) the information on thefunction-executing instruction (e.g., execution identifying informationon the second user interface 1030), and may wait for the reception ofthe first user input corresponding thereto (e.g., a configured gestureinput corresponding to the acceptance or rejection, a physical buttoninput for the acceptance or rejection, a software-based button input forthe acceptance or rejection, or the like). In various embodiments of thepresent disclosure, the operation of waiting for the first user inputmay be omitted. For example, when the wearable device 600 receives thefunction-executing instruction, the wearable device 600 may directlyexecute and display the second user interface 1030 in response to thefunction-executing instruction without waiting for the first user input.

In various embodiments, the electronic device 400 and the wearabledevice 600 may perform a data communication operation, such as making arequest for the related information (e.g., files selected for the filetransfer) necessary for the provision of the second user interface 1030and the reception thereof in response to the first user input or thedirect execution of the second user interface 1030.

According to various embodiments, if the execution of the second userinterface 1030 is accepted by the user, the wearable device 600 mayexecute and display the second user interface 1030 (e.g., a userinterface capable of displaying a clipboard area, which is selected forthe file transfer and temporarily stores the same, and controlling thesame). In various embodiments, in instances in which the second userinterface 1030 is in progress by the interworking between the wearabledevice 600 and the electronic device 400, the operation above may beomitted.

According to various embodiments, when the second user input is receivedwhile the second user interface 1030 is displayed, the wearable device600 may execute the related operation. According to an embodiment, thewearable device 600 may transmit, to the electronic device 400, acontrol signal to instruct the files of the clipboard to be transferredto the other electronic device 550 through a second user interface 1030or to instruct at least some of the files of the clipboard to beselected or deleted.

According to various embodiments, the electronic device 400 may performvarious operations, such as transferring the files to the otherelectronic device 550, selecting the files, or deleting the selectedfiles, in response to the control signal.

According to various embodiments, the other electronic device 550 maydisplay the user interface related to the file transfer function throughthe display 1050 when the other electronic device 550 is connected withthe electronic device 400, or may display the user interface related tothe progress status through the display 1050 in response to theinitiation of the file transfer of the electronic device 400.

FIG. 11 is a flowchart of an example of a process, according to variousembodiments of the present disclosure.

Referring to FIG. 11, in operation 1101, the controller 480 may beconnected with the wearable device 600 based on a configuredcommunication scheme.

In operation 1103, the controller 480 may detect an event associatedwith the device 500. According to various embodiments, the controller480 may detect a pairing event when the device 500 is connected to theelectronic device 400.

Alternatively, when the connection with the device 500 in the connectionis terminated, the controller 480 may detect a pairing release event.

In operation 1105, the controller 480 may identify a function related tothe device 500 in response to the event detection. According to variousembodiments, the controller 480 may identify the type of device 500, andmay determine the executable function according to the type of device500. In various embodiments of the present disclosure, when thecontroller 480 determines a function that can be performed together withthe device 500, the controller 480 may determine whether or not thefunction can be performed by the interworking with the wearable device600 as well. According to various embodiments, the controller 480 maydetermine whether or not a user interface dedicated to the wearabledevice 600, which matches the function that can be performed by thedevice 500, exists.

In operation 1107, the controller 480 may display the user interface(e.g., the first user interface), which is related to the function thatcan be performed by the device 500

In operation 1109, the controller 480 may transmit a function-executinginstruction corresponding to the function to the wearable device 600.According to various embodiments, the controller 480 may transmit, tothe wearable device 600, the function-executing instruction forperforming the interworking function with the wearable device 600 inresponse to the event associated with the device 500. In variousembodiments, the function-executing instruction may include aninstruction for causing the wearable device 600 to execute the relatedfunction and to output a user interface (e.g., the second userinterface) corresponding to the related function, in response to theevent.

In operation 1111, the controller 480 may execute the correspondingoperation. According to various embodiments, after transmitting thefunction-executing instruction to the wearable device 600, thecontroller 480 may control the interworking function that is in progresswith the device 500 in response to the control signal received from thewearable device 600.

FIG. 12 is a flowchart of an example of a process, according to variousembodiments of the present disclosure.

Referring to FIG. 12, in operation 1201, the controller 480 may beconnected to the wearable device 600.

In operation 1203, the controller 480 may detect an event associatedwith the device 500. For example, the controller 480 may detect theevent in response to the connection of the device 500 with theelectronic device 400 to be communicable, or the disconnection of thedevice 500 to disable the communication.

In operation 1205, when the controller 480 detects the event, thecontroller 480 may determine the type of event to correspond to theconnection or disconnection of the device 500, and in operation 1207,the controller 480 may determine whether the event is a pairing event ora pairing release event based on the determination result.

If the controller 480 determines that the event is a pairing event inoperation 1207 (“YES” in operation 1207), the controller 480 maydetermine the type of device 500 that is connected to the electronicdevice 400 in operation 1209.

If the controller 480 determines the type of device 500, the controller480 may perform a search for a configured function that can beassociated with the device 500 (a matching function) in operation 1211,and the controller 480 may determine whether or not the correspondingfunction exists in operation 1213. According to various embodiments, thecontroller 480 may determine whether or not a function, which can beexecuted by the interworking with the device 500, or a function, whichis predetermined as an interworking function with the device 500,exists.

If the controller 480 determines that there is no matching function inoperation 1213 (“NO” in operation 1213), the controller 480 may causethe electronic device 400 to solely (independently) execute the functionin operation 1215. For example, the controller 480 may cause theelectronic device 400 to independently execute the function rather thanexecuting the function in cooperation with the wearable device 600.According to other embodiments, if the controller 480 determines thatthere is no matching function in operation 1213 (“NO” in operation1213), the controller 480 may provide the wearable device 500 withinformation by which a function, which can be executed by theinterworking with the device 500, may be obtained (installed). Forexample, the controller 480 may provide an application installation URLaddress, which is related to the function that matches the device 500,in the form of a pop-up window or other UIs.

If the controller 480 determines that there is a matching function inoperation 1213 (“YES” in operation 1213), a user interface (e.g., thefirst user interface), which is related to the function that matches thedevice 500, may be displayed in operation 1217.

In operation 1219, the controller 480 may transmit a function-executinginstruction corresponding to the function to the wearable device 600.According to various embodiments, the controller 480, in response to theevent associated with the device 500, may cause the wearable device 600to execute the related function corresponding to the function and todisplay a user interface (e.g., the second user interface) correspondingto the related function.

In operation 1221, the controller 480 may determine whether or not acontrol signal is received from the wearable device 600. According tovarious embodiments, after transmitting the function-executinginstruction, the controller 480 may wait to receive a control signalthat is related to the function that is executed by the wearable device600 by the interworking with the device 500, and the wearable device 600may transmit the control signal to the electronic device 400 in responseto a user input.

If the control signal is received from the wearable device 600 inoperation 1221 (“YES” in operation 1221), the controller 480 may executethe function in response to the received control signal in operation1223. In various embodiments of the present disclosure, the controller480 may process the control (e.g., the function control operationsaccording to the examples of FIG. 7 to FIG. 10) corresponding to thecontrol signal in the function that is in progress by the interworkingwith the device 500.

If the control signal is not received from the wearable device 600 inoperation 1221 (“NO” in operation 1221), the controller 480 may executethe corresponding operation in operation 1225. According to variousembodiments, the controller 480 may continue to process the functionthat is in progress by the interworking with the connected device 500while waiting for a control signal received from the wearable device600.

If the controller 480 determines that the event is the pairing releaseevent in operation 1207 (“NO” in operation 1207), the controller 480 maydetect whether or not a function is in progress by the interworking withthe wearable device 600 in operation 1231.

If the controller 480 determines that the function is in progress by theinterworking in operation 1231 (“YES” in operation 1231), the controller480 may transmit a function-end instruction to the wearable device 600in operation 1233. According to various embodiments, the controller 480may cause the wearable device 600 to terminate the function in progressand to end the display of the user interface (e.g., the second userinterface) corresponding to the function.

After transmitting the function-end instruction, the controller 480 mayexecute the corresponding operation in operation 1225. According tovarious embodiments, the controller 480 may: terminate the function inprogress by the interworking with the device 500; hide the userinterface (e.g., the first user interface), which is displayed,according thereto; and switch to another user interface {e.g., the userinterface (the home screen user interface), which is related to thefunction that is previously performed} to then be displayed.

If the controller 480 determines that the function is not in progress bythe interworking in operation 1231 (“NO” in operation 1231), thecontroller 480 may execute the corresponding operation in operation1225. According to various embodiments, the controller 480 may terminatethe function that is in progress by the interworking with the device500, and thus may convert the user input to then be displayed.

FIG. 13 is a flowchart of an example of a process, according to variousembodiments of the present disclosure.

Referring to FIG. 13, in operation 1301, the controller 630 of thewearable device 600 may be connected with the electronic device 400based on a configured communication scheme.

In operation 1303, the controller 630 may receive a function controlinstruction from the electronic device 400 while it is connected withthe electronic device 400.

If the function control instruction is received, the controller 630 maydetermine the received function control instruction in operation 1305,and the controller 630 may determine whether the function controlinstruction is a function-executing instruction (e.g., an instructionfor executing the function) or a function-end instruction (e.g., aninstruction for terminating the function) based on the determinationresult in operation 1307.

If the controller 630 determines that the function control instructionis a function-end instruction in operation 1307 (“NO” in operation1307), the controller 630 may terminate the function that is in progressby the interworking with the electronic device 400 in response to thefunction-end instruction in operation 1309.

After terminating the function, the controller 630 may execute thecorresponding operation in operation 1311. According to variousembodiments, the controller 630, in response to the function-endinstruction, may convert the user interface (e.g., the second userinterface) into another user input to then be displayed upon thetermination of the function, or may turn off the display unit upon thetermination of the function.

If the controller 630 determines that the function control instructionis a function-executing instruction in operation 1307 (“YES” inoperation 1307), the controller 630 may display a user interface (e.g.,the second user interface) in operation 1313. According to variousembodiments, the controller 630 may execute a related functioncorresponding to the function-executing instruction, and may display auser interface (e.g., the second user interface) corresponding to therelated function.

In operation 1315, the controller 630 may determine whether or not auser input is received based on the user interface. According to variousembodiments, after displaying the user input, the controller 680 mayreceive a user input to control the function that is in progress by theinterworking between the electronic device 400 and the device 500through the user interface.

If the user input is not received in operation 1315 (“NO” in operation1315), the controller 630 may execute the corresponding operation inoperation 1311. According to various embodiments, the controller 630 maywait for a user input while continuing to display the user interface. Inaddition, if the user input is not received within a predetermined timeperiod, the controller 630 may control to turn off the display unit.

If the user input is received in operation 1315 (“YES” in operation1315), the controller 630 may execute the operation by the interworkingwith the electronic device 400 in operation 1317. According to variousembodiments, when the user input is received, the controller 630 maydetermine a function corresponding to the user input, and may transmit acontrol signal corresponding to the determined function to theelectronic device 400. In addition, the controller 630 may apply therelated component to the user interface to then be displayed in responseto the user input.

Meanwhile, although it is not shown in FIG. 13, according to variousembodiments of the present disclosure, when the function-executinginstruction is received from the electronic device 400, the controller630 of the wearable device 600 may output information that is related tothe function-executing instruction. For example, the controller 630 mayprovide the user with the feedback based on at least some of thedisplay, the vibration, or the alarm with respect to the reception ofthe function-executing instruction. The controller 630, in response tothe information output in relation to the function-executinginstruction, may receive a user input {e.g., the first user input (e.g.,an input corresponding to the acceptance or rejection of the functionexecution)}, and may perform an operation of displaying the userinterface in response to the user input.

As described above, an operating method of an electronic device 400,according to various embodiments of the present disclosure, may include:detecting an event by a connection of a device 500 while being connectedwith a wearable device 600; determining the type of device 500, which isrelated to the event; determining a function of the wearable device 600,which matches the type of device 500; and transmitting, to the wearabledevice 600, an executing instruction for executing the function in thewearable device 600.

As described above, an operating method of a wearable device 600,according to various embodiments of the present disclosure, may include:receiving an executing instruction from a connected electronic device400; executing a function corresponding to the executing instruction anddisplaying a related user interface (e.g., the second user interface);receiving a user input through the user interface; and transmitting acontrol signal related to the user input to the electronic device 400.In various embodiments of the present disclosure, the user input mayinclude an input (e.g., the second user input), which is receivedthrough the user interface (e.g., the second user interface that isdisplayed on the wearable device 600) in relation to the control of theoperation or function of the electronic device 400.

As described above, an interworking method of electronic devices,according to various embodiments of the present disclosure, may include:performing a connection between an electronic device 400 and a wearabledevice 600; detecting an event associated with a connection of a device500 in the electronic device 400; displaying the first user interfacethat is related to a function that matches the device 500 in theelectronic device 400, and transmitting an executing instructioncorresponding to the function to the wearable device 600; displaying thesecond user interface that is related to the function in response to thereception of the executing instruction in the wearable device 600;transmitting, to the electronic device 400, a control signalcorresponding to the user input received based on the second userinterface in the wearable device 600; and executing an operation relatedto the function by the interworking with the device 500 in response tothe receipt of the control signal in the electronic device 400.

The electronic device and the method thereof, according to variousembodiments of the present disclosure, may execute the operation relatedto the event by the interworking with the wearable device connected withthe electronic device in response to the event of the connection ordisconnect of the device in the electronic device.

According to various embodiments of the present disclosure, theelectronic device may detect a related event when a particular device isconnected or disconnected, and may determine an execution method of afunction corresponding to the detected event. The electronic device mayexecute the function for the event by the interworking with the wearabledevice or may solely execute the same, based on the result of thedetermination operation. Accordingly, the user may use the device moreeasily without additional manipulation based on at least one of theelectronic device or the wearable device.

According to various embodiments of the present disclosure, the user maybe provided with various user experiences through the interworking ofthe electronic device, the device, and the wearable device, and theexecution of the interworking function according thereto.

According to various embodiments of the present disclosure, an optimumenvironment for allowing the electronic devices to interwork with eachother and executing the interworking function corresponding thereto maybe implemented in order to thereby improve the user's convenience, andthe usability, the convenience, the accessibility, and thecompetitiveness of the electronic device.

FIGS. 1-13 are provided as an example only. At least some of theoperations discussed with respect to these figures can be performedconcurrently, performed in different order, and/or altogether omitted.It will be understood that the provision of the examples describedherein, as well as clauses phrased as “such as,” “e.g.”, “including”,“in some aspects,” “in some implementations,” and the like should not beinterpreted as limiting the claimed subject matter to the specificexamples.

The above-described aspects of the present disclosure can be implementedin hardware, firmware or via the execution of software or computer codethat can be stored in a recording medium such as a CD-ROM, a DigitalVersatile Disc (DVD), a magnetic tape, a RAM, a floppy disk, a harddisk, or a magneto-optical disk or computer code downloaded over anetwork originally stored on a remote recording medium or anon-transitory machine-readable medium and to be stored on a localrecording medium, so that the methods described herein can be renderedvia such software that is stored on the recording medium using a generalpurpose computer, or a special processor or in programmable or dedicatedhardware, such as an ASIC or FPGA. As would be understood in the art,the computer, the processor, microprocessor controller or theprogrammable hardware include memory components, e.g., RAM, ROM, Flash,etc. that may store or receive software or computer code that whenaccessed and executed by the computer, processor or hardware implementthe processing methods described herein. In addition, it would berecognized that when a general purpose computer accesses code forimplementing the processing shown herein, the execution of the codetransforms the general purpose computer into a special purpose computerfor executing the processing shown herein. Any of the functions andsteps provided in the Figures may be implemented in hardware, softwareor a combination of both and may be performed in whole or in part withinthe programmed instructions of a computer. No claim element herein is tobe construed under the provisions of 35 U.S.C. 112, sixth paragraph,unless the element is expressly recited using the phrase “means for”.

Moreover, the embodiments disclosed in this specification are suggestedfor the description and understanding of technical content but do notlimit the range of the present disclosure. Accordingly, the range of thepresent disclosure should be interpreted as including all modificationsor various other embodiments based on the technical idea of the presentdisclosure.

What is claimed is:
 1. An electronic device comprising: a memory; acommunication unit for exchanging communications with a wearable deviceand an external device; and at least one processor that is operativelycoupled to the memory, configured to: detect an event that is associatedwith a connection with the external device; identify a function that isassociated with the external device in response to the event; andtransmit to the wearable device an instruction for executing thefunction, wherein the instruction is transmitted via the communicationsunit.
 2. The electronic device of claim 1, wherein the communicationunit includes at least one of a wired communications module and awireless communications module.
 3. The electronic device of claim 1,wherein: the wearable device is connected to the electronic device viaone of a wired or wireless communication; and the external deviceincludes at least one of an electronic pen, earphones, a charger, and adisplay device.
 4. The electronic device of claim 1, wherein the atleast one processor is further configured to control execution of thefunction.
 5. The electronic device of claim 1, wherein the at least oneprocessor is further configured to: detect whether the function isavailable in the wearable device, and if the function is not availablein the wearable device, provide the wearable device with information forinstalling the function.
 6. The electronic device of claim 1, whereinthe at least one processor is further configured to: detect whether thefunction is available in the wearable device; if the function isavailable in the wearable device, display a first user interface that isrelated to the function; and execute an operation that is related to thefunction in response to a control signal that is received from thewearable device, the control signal being generated based on an input toa second user interface that is displayed by the wearable device.
 7. Theelectronic device of claim 6, wherein the first user interface includesa first user interface component, and the second user interface includesa second user interface component that is associated with the first userinterface component.
 8. The electronic device of claim 1, wherein the atleast one processor is further configured to transmit to the wearabledevice an instruction for terminating the function in response todetecting that the connection with the external device is terminated. 9.A method for use in an electronic device, comprising: establishing aconnection with an external device; detecting an event that isassociated with the connection with the external device; identifying afunction that is associated with the external device in response to theevent; and transmitting to a wearable device an instruction forexecuting the function.
 10. The method of claim 9, further comprisingdisplaying a first user interface corresponding that is associated withthe function.
 11. The method of claim 10, wherein the instruction, whenexecuted by the wearable device, causes the wearable device to display asecond user interface that is associated with the first user interface.12. The method of claim 11, wherein the first user interface includes afirst user interface component, and the second user interface includes asecond user interface component that is associated with the first userinterface component.
 13. The method of claim 9, further comprising:receiving a control signal from the wearable device; and controlling theexecution of an operation related to the function in response to thecontrol signal.
 14. The method of claim 9, further comprising detectingwhether the function is available in the wearable device.
 15. The methodof claim 14, further comprising: if the function is available,displaying a first user interface that is associated with the function;and executing an operation that is related to the function in responseto a control signal that is received from the wearable device, whereinthe wearable device is configured to display a second user interfacethat is associated with the first user interface, and wherein thecontrol signal is generated based on the second user interface.
 16. Themethod of claim 9, further comprising transmitting to the wearabledevice an instruction for terminating the function in response todetecting that the connection with the external device is terminated.17. A method for use in a wearable device, comprising: receiving aninstruction from an electronic device; executing a functioncorresponding to the instruction and displaying a user interfaceassociated with the function; receiving a first input via the userinterface; and transmitting a control signal to the electronic device inresponse to the first input.
 18. The method of claim 17, furthercomprising: displaying information associated with the instruction; andreceiving a second input corresponding to the information, wherein theuser interface is displayed based on the second input, and wherein thesecond input includes at least one of a posture change input, abiometric recognition input, a button input, or a touch gesture input.19. A method comprising: establishing a connection between an electronicdevice and a wearable device; detecting an event associated with theconnection; displaying, by the electronic device, a first user interfacethat is related to a function that matches an external device, andtransmitting to the wearable device an instruction for executing thefunction; displaying, by the wearable device, a second user interfacethat is related to the function in response to the instruction forexecuting the function, transmitting, to the electronic device, acontrol signal corresponding to user input received via the second userinterface; and executing, by the electronic device, an operation relatedto the function in response to the control signal, wherein the operationis executed in cooperation with the external device.
 20. The method ofclaim 19, wherein the first user interface includes a first userinterface component, and the second user interface includes a seconduser interface component that is associated with the first userinterface component.
 21. A computer-readable storage medium storing oneor more programs comprising instructions which, when executed by atleast one processor, cause the at least one processor to execute themethod according to claim
 9. 22. A computer-readable storage mediumstoring one or more programs comprising instructions which, whenexecuted by at least one processor, cause the at least one processor toexecute the method according to claim 17.